Hi,
Sensu remediation getting triggered again and again evem when not required.
check_display.json:
{
“checks”: {
“check_display”: {
“command”: “/etc/sensu/plugins/check-display.rb -p PROC”,
“interval”: 60,
“handlers”: [“remediator”],
“occurrences”: 1,
“standalone”: true,
“refresh”: 60,
“remediation”: {
“light_remediation_display”: {
“occurrences”: [1],
“severities”: [“WARNING”]
}
}
},
“light_remediation_display”: {
“command”: “/etc/sensu/handlers/fixdisplay.rb”,
“standalone”: true,
“interval”: 60,
“publish”: false
}
}
}
I have tried setting severities as 1,2 “ERROR”, OK no change. Is there something missing here?
···
–
Mishal
The docs say it "severities" is a list of integers:https://github.com/sensu/sensu-community-plugins/blob/master/handlers/remediation/sensu.rb#L12
It sounds like [1, 2] is correct for this use case.
Can you provide sensu-server or sensu-client logs after changing that
The only other thing I can think of is the subscribers key. The
Also the remediation check should not be standalone, it is designed to
Check out the documentation for working example of how to use thishttps://github.com/sensu/sensu-community-plugins/blob/master/handlers/remediation/sensu.rb#L26-L63
···
On Thu, Jul 2, 2015 at 8:22 AM, Mishal Dholakia <mishal.dholakia@gmail.com> wrote:
Hi,
Sensu remediation getting triggered again and again evem when not required.
check_display.json:
{
"checks": {
"check_display": {
"command": "/etc/sensu/plugins/check-display.rb -p PROC",
"interval": 60,
"handlers": ["remediator"],
"occurrences": 1,
"standalone": true,
"refresh": 60,
"remediation": {
"light_remediation_display": {
"occurrences": [1],
"severities": ["WARNING"]
}
}
},
"light_remediation_display": {
"command": "/etc/sensu/handlers/fixdisplay.rb",
"standalone": true,
"interval": 60,
"publish": false
}
}
}
I have tried setting severities as 1,2 "ERROR", OK no change. Is there
--
Mishal
I suppose remedition only works with non standalone checks?
See
opened 09:48PM - 21 Jan 15 UTC
closed 04:51AM - 26 Sep 17 UTC
Feature
I would like to have an optional recovery command executed by the sensu client. … So I would define check like "fs usage" and a recovery would be "find all old files and delete them".
Options like recovery timeout and recovery tries would ensure that errors which can not be recovered still create tickets.
···
Am Sonntag, 5. Juli 2015 02:46:12 UTC+2 schrieb Kyle Anderson:
The docs say it “severities” is a list of integers:
https://github.com/sensu/sensu-community-plugins/blob/master/handlers/remediation/sensu.rb#L12
It sounds like [1, 2] is correct for this use case.
Can you provide sensu-server or sensu-client logs after changing that
to aid in debugging?
The only other thing I can think of is the subscribers key. The
remediation command should subscribe to nothing (“subscribers”:
I don’t see that in the config, but I’m pretty sure that is going to
be the default anyway? Doesn’t hurt to be explicit that nothing should
be susbcribing to light_remediation_display.
Also the remediation check should not be standalone, it is designed to
be initiated on-demand and not as a standalone check.
Check out the documentation for working example of how to use this
remediation handler if you have not already:
https://github.com/sensu/sensu-community-plugins/blob/master/handlers/remediation/sensu.rb#L26-L63
On Thu, Jul 2, 2015 at 8:22 AM, Mishal Dholakia > > mishal....@gmail.com wrote:
Hi,
Sensu remediation getting triggered again and again evem when not required.
check_display.json:
{
“checks”: {
“check_display”: {
“command”: “/etc/sensu/plugins/check-display.rb -p PROC”,
“interval”: 60,
“handlers”: [“remediator”],
“occurrences”: 1,
“standalone”: true,
“refresh”: 60,
“remediation”: {
“light_remediation_display”: {
“occurrences”: [1],
“severities”: [“WARNING”]
}
}
},
“light_remediation_display”: {
“command”: “/etc/sensu/handlers/fixdisplay.rb”,
“standalone”: true,
“interval”: 60,
“publish”: false
}
}
}
I have tried setting severities as 1,2 “ERROR”, OK no change. Is there
something missing here?
–
Mishal
As far as I understand it, the "normal" check can be standalone, but
···
On Wed, Jul 15, 2015 at 1:07 AM, Philipp H <hellmi@gmail.com> wrote:
I suppose remedition only works with non standalone checks?
SeeRecovery command for each check · Issue #850 · sensu/sensu · GitHub
Am Sonntag, 5. Juli 2015 02:46:12 UTC+2 schrieb Kyle Anderson:
The docs say it "severities" is a list of integers:
https://github.com/sensu/sensu-community-plugins/blob/master/handlers/remediation/sensu.rb#L12
It sounds like [1, 2] is correct for this use case.
Can you provide sensu-server or sensu-client logs after changing that
The only other thing I can think of is the subscribers key. The
Also the remediation check should not be standalone, it is designed to
Check out the documentation for working example of how to use this
https://github.com/sensu/sensu-community-plugins/blob/master/handlers/remediation/sensu.rb#L26-L63
On Thu, Jul 2, 2015 at 8:22 AM, Mishal Dholakia >> <mishal....@gmail.com> wrote: