is_volatile directive for active service

[satheesh19870819]

Hello Team,
I would like to know whether this directive is_volatile can work on active checks .

If not , is there any way to make my active service OK state before next normal check interval

[scottwilkerson]

Yes it does

[satheesh19870819]

Hello scottwilkerson

Thank you for your info . I am creating the definition like follows . But its not turning the service to OK state . this service is a log monitoring service so at every normal interval it should trigger new alert . So i thought of making the service OK before the next normal check interval .

Code: Select all

max_check_attempts              1
        normal_check_interval           10
        retry_check_interval            10
        process_perf_data               0
        notification_options            c,r
        is_volatile                     1
        check_freshness                 1
        freshness_threshold             300

Kindly let me know whether am doing any error .

[scottwilkerson]

do you have a check_command defined? That is what is going to be run at the freshness_interval

Usually you would add a check_dummy command to the definition like the following:

Code: Select all

check_dummy!0!"Reset to OK"

[satheesh19870819]

Its a active check .
The defined check command monitors log file at client every 10 minutes . i think check command cannot be changed , it should point the logfile monitoring .

is there a way to use is_volatile without freshness threshold .

Also am wondering check_dummy can be used for active checks . We are using it only for passive check where to commands triggered from nagios side .

[scottwilkerson]

I'm confused, if it is an active check, why would you want to

make my active service OK state before next normal check interval

?


See:
https://assets.nagios.com/downloads/nag ... vices.html

[scottwilkerson]

is there a way to use is_volatile without freshness threshold .

yes. freshness is not required

[satheesh19870819]

i have a check which monitors log file . every 30 minutes it will monitor the file and if there is any new error message in log then it will alert . Once alerted admin will acknowledge the alert and start working on it .
During the next check if there is new error entry in log for different message (not the old error) , then we need new alert .

Since its ACK no new alerts will happen without state change . So i thought of making it OK before next normal check interval .

[scottwilkerson]

There is not function to make it OK before the next check attempt, unless instead of acknowledging the alert the person just sends a passive check of OK which you can do from the interface.

[satheesh19870819]

ok thank you for the clear information .

So in general shall we say like is_volatile and freshness will not work for active checks and they are meant for passive checks .