Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support
  3. SYS_AGENT_UNREACHABLE alarm not until 3 polls fail

SYS_AGENT_UNREACHABLE alarm not until 3 polls fail

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 32.3k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • T
    T
    tarnmensch
    wrote on last edited by
    #1

    Hello everyone!

    Let me first thank you for a great piece of software as well as a very useful forum! I've been using NetXMS for about 2 months now, so I'm still learning a lot here.

    My configuration works quite well, but here's my problem: To get a warning if an agent fails, I included SYS_AGENT_UNREACHABLE in the event processing policy, but I can't find a way to avoid alarms that emerge from reboots or just short network issues. Is there any way to set the alarm to wait for 3 failed polls like you can do for every data collector as well as the general node reachable state?

    Sorry if I overlooked some solution here. The only idea I can think of is to set the AgentCommandTimeout variable to some very high value, but I think this could influence the NetXMS behaviour generally.

    Thanks a lot, bye!

    1 Reply Last reply
    0
    • V
      V
      Victor Kirhenshtein
      wrote on last edited by
      #2

      Hi,

      instead of processing SYS_AGENT_UNREACHABLE event you can collect internal parameter AgentStatus. It returns 0 if agent is connected and 1 if unreachable. Then you can use thresholds as usual to generate alarm only if agent is unreachable for more then specific time period.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • T
        T
        tarnmensch
        wrote on last edited by
        #3

        Hello Victor,

        Thank you for your reply and the great work - I finally found time to change to the AgentStatus parameter.

        Best regards

        1 Reply Last reply
        0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        Powered by NodeBB Contributors
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups