Ad Widget

Collapse

nodata doesn't seem to work

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • cioris
    Member
    • Oct 2008
    • 30

    #1

    nodata doesn't seem to work

    Hi,

    I set a trigger to detect if one of the server is down. Here is the trigger:

    {Template_Windows_Servers_Remote:agent.ping.nodata (120)}=1

    The ping is set to run every 30 seconds, but when I turn off the agent or the entire server, the trigger does not become active.

    Anything wrong with this trigger? Thanks

    BTW, I'm running server 1.6 with windows agent 1.4.6
  • cioris
    Member
    • Oct 2008
    • 30

    #2
    Hmmm... I found the problem!!!! It is in the trigger properties

    There is no problem with nodata(), but with the triggers templates in 1.6
    I have defined a template for my windows servers. After that I decided to disable some of the triggers. It looks like the enable/disable property is not passed correctly to the associated servers. In fact, if I look at the template everything is ok, but if I look at a secific machine using that template, the enable/disable is completly wrong. Some of the trigger appear enable in the template, but they are disable for some machines and vice versa. Please be aware that I didn't manually enabld/disabled any trigger for any server. I just applied the template to some of my machines.

    At the same time I saw that enable/disable seleted button has no effect for triggers (it works fine for items). You can try to select few triggers and after that just click on disable selected. You will see that the status is not updated, even in the details section there are a lot of messages telling that the triggers were updated.

    This can create a huge issues when big sites are monitored. You have to manually check the enable/disable option for every single machine.

    You can also check to enable/disable a trigger in a template. The associated machines will not be updated.

    I hope this will help, Thanks

    Comment

    Working...