Ad Widget

Collapse

unexpected trigger behavior

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • XXeR
    Junior Member
    • Jan 2008
    • 12

    #1

    unexpected trigger behavior

    hey folks, i have a couple trigger/action pairs set up on a web service as follows:

    net.tcp.service[http].max(120)}=0 --> action restart
    net.tcp.service[http].max(300)}=0 --> action alert

    the idea is that if the port is completely unresponsive for 120s, then an action is in place to restart the web service. if it's completely unresponsive for 300s, then send me an alert.

    the problem is that i'll sometimes get the alert BEFORE the restart of the service is ever attempted...which seems like it should be impossible.

    what am i missing? is there a better way to achieve this?

    thanks!
  • XXeR
    Junior Member
    • Jan 2008
    • 12

    #2
    bump, anyone?

    Comment

    • XXeR
      Junior Member
      • Jan 2008
      • 12

      #3
      one more time

      Comment

      • tim.mooney
        Senior Member
        • Dec 2012
        • 1427

        #4
        How often is the item being checked?

        Have you looked through the list of events (Monitoring->Events), to verify that both actions are even firing?

        Comment

        Working...