I am seeing this type of history in my sensu-checks requently
history
0, 0, 2, 0, 0, 2, 0, 0, 2, 0, 0, 2, 0, 0, 2, 0, 0, 2, 0, 2, 0
and output as:
CheckHttp CRITICAL: xxxxxxxxxxxxxxxxx
but, when I search of the CRITICAL ouput in the client logs, I can even find not even one message in logs
I am seeing many critcal issues in my events tab.
How can I resolve this.
Hi Imran,
what OS are you on? I would first check what your LOG_LEVEL setting is for sensu. On Linux you can check
root@sensu2:~# cat /etc/default/sensu
EMBEDDED_RUBY=true
LOG_LEVEL=info
SERVICE_MAX_WAIT=“10”
PATH=$PATH
The default LOG_LEVEL is INFO so if you haven’t changed anything you should see all check results in sensu-api.log
I’m running Debian so the log files are in /var/log/sensu/
More info on Sensu configuration https://sensuapp.org/docs/latest/reference/configuration.html#sensu-service-script-configuration-variables
-AB
On Monday, 19 December 2016 11:18:53 UTC+1, IMRAN SHAIK wrote:
I am seeing this type of history in my sensu-checks requently
history
0, 0, 2, 0, 0, 2, 0, 0, 2, 0, 0, 2, 0, 0, 2, 0, 0, 2, 0, 2, 0
and output as:
CheckHttp CRITICAL: xxxxxxxxxxxxxxxxx
but, when I search of the CRITICAL ouput in the client logs, I can even find not even one message in logs
I am seeing many critcal issues in my events tab.
How can I resolve this.