-
Notifications
You must be signed in to change notification settings - Fork 17
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
fixed post/incident bug #4
Conversation
and fixed a typo |
Thank you! Yes, it fixes the typo #2 I will try it today and merge if it works :) |
It works for #3 but an other problem happens for me when trying to update the incident:
The incident is in the database but is not returned by the API, I don't know what can be wrong. I am using Cachet 2.0.3. I will branch and try something... |
Can you show your test case? I've been raising 'OK' 'HARD' incidents and then closing it without issues so maybe it's a particular incident or component_status causing it. |
Hi dpina000, I tried you code but it seems I am also seeing the same issue which mpellegrin is taking about. Actually I am using the code against Icinga2 which has compatibility with Nagios/Icinga1 plugins. With your code the incidents are getting opened on the Cachet Status Page and but are not getting closed after the recovery or no change in the Component Status even in Ok + Soft state. For Icinga2 there are changes in the argument numbers. But rest of the code remains the same. $cachet_component = $argv[2]; |
This is how I am trying to create/update/closed the incidents Critical + Hard state Ok + Soft state Ok + Hard State |
Hi thanks for the commit now I am able to the the component status changed. |
mpellegrin#4 Signed-off-by: David Galloway <[email protected]>
This fixed issue #3:
#3