Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dev.icinga.com #13197] API: Command process-check-result fails if it contains performance data #4786

Closed
icinga-migration opened this issue Nov 15, 2016 · 2 comments · Fixed by #6077
Assignees
Labels
area/api REST API bug Something isn't working
Milestone

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/13197

Created by elippmann on 2016-11-15 09:33:16 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2016-11-15 09:33:16 +00:00 (in Redmine)

Icinga Version: 2.5.4
Backport?: Not yet backported
Include in Changelog: 1

Icinga 2 fails w/ the following error: Error: Cannot convert value of type 'String' to an object.

@icinga-migration icinga-migration added bug Something isn't working area/api REST API labels Jan 17, 2017
@dnsmichi dnsmichi self-assigned this Jan 16, 2018
@dnsmichi
Copy link
Contributor

dnsmichi commented Feb 6, 2018

$ curl -k -s -u root:icinga 'https://localhost:5665/v1/actions/process-check-result' -X POST -H 'Accept: application/json' -d '{ "type": "Service", "filter": true, "plugin_output": "abc", "performance_data": "key1=9", "exit_status": 2 }'

@dnsmichi
Copy link
Contributor

dnsmichi commented Feb 6, 2018

screen shot 2018-02-06 at 15 22 51
screen shot 2018-02-06 at 15 22 56

dnsmichi pushed a commit that referenced this issue Feb 6, 2018
This is how data is coming from Icinga Web 2 and still a valid input
type.

fixes #4786
@dnsmichi dnsmichi added this to the 2.9.0 milestone Feb 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api REST API bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants