You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have ldap_sync_remediation remediation check for ldap_sync check.
ldap_sync_remediation check will execute only once on 3 successful failures of ldap_sync.
In some cases, there might be a chance of ldap_sync_remediation check failure. In that case, "ldap_sync_remediation" checks are stuck on Uchiwa dashboard. Is there a way to auto-resolve(should be automatically removed from Uchiwa dashboard event section) when ldap_sync_remediation fails.
I mentioned "force_resolve": true for this. But seems it is now working.
We have ldap_sync_remediation remediation check for ldap_sync check.
ldap_sync_remediation check will execute only once on 3 successful failures of ldap_sync.
In some cases, there might be a chance of ldap_sync_remediation check failure. In that case, "ldap_sync_remediation" checks are stuck on Uchiwa dashboard. Is there a way to auto-resolve(should be automatically removed from Uchiwa dashboard event section) when
ldap_sync_remediation fails.
I mentioned "force_resolve": true for this. But seems it is now working.
{
"checks": {
"ldap_sync": {
"command": "export PYTHON_EGG_CACHE=/etc/sensu/plugins/tmp;/etc/sensu/plugins/check_ldap_sync.py -q -n ldap://localhost:1389 ldap://localhost:389 -t 1800",
"interval": 600,
"timeout": 120,
"ttl": 2000,
"contacts": [ "team-houston" ],
"subscribers": [
"csa-local"
],
"low_flap_threshold": 20,
"high_flap_threshold": 40,
"remediation": {
"ldap_sync_remediation": {
"occurrences": ["3"],
"severities": [1, 2]
}
}
},
"ldap_sync_remediation": {
"command": "sudo -u root /usr/local/bin/python /etc/sensu/plugins/run_ldap_stf1.py -s 'wnccsmmgmt1'",
"publish": false,
"interval": 180,
"timeout": 300,
"force_resolve": true,
"contacts": [ "team-houston" ],
"occurrences": 1,
"handler": "email",
"subscribers": []
}
}
}
The text was updated successfully, but these errors were encountered: