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. Alert Notifier does not match alarm viewer or in Console

Alert Notifier does not match alarm viewer or in Console

Scheduled Pinned Locked Moved Support
2 Posts 2 Posters 22.6k 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.
  • K
    K
    keefbeef
    wrote on last edited by
    #1

    I have noticed that the alarm notifer has identified a number of alarms that do not appear in either the alarms viewer or console.  Specifially it shows that a number of nodes have dropped out late at night, but I assume that they have came back on-line not much later.

    Are these not appearing in the console because the nodes have come back online?  If this is the case, is there a way to maintain these alarms so that I know that they have occured - such as a history of all alarms created against a node?

    It's a smart piece of software BTW...

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

      It's actually a bug in alarm notifier - it does not update alarm list correctly.

      For knowing that node was offline for some time and then go back online, you can do the following:
      Instead of terminating node down alarm when SYS_NODE_UP event received, generate new alarm with NORMAL priority which will replace "Node down" alarm. Than you will know that node was down for some time. Then you have 3 options to terminate those "Node up" alarms:

      1. Terminate them manually;
      2. Create a script that will use nxalarm command line utility to periodically read active alarms and terminate "Node up" alarms which are older than some time period;
      3. Set alarm timeout for "Node up" alarms and terminate them when alarm timeout event comes.

      Best regards,
      Victor

      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