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. Automatic Alarm Resolve

Automatic Alarm Resolve

Scheduled Pinned Locked Moved Support
5 Posts 2 Posters 57.4k 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.
  • C
    C
    CrUser
    wrote on last edited by
    #1

    Hi,

    I have one problem about automatic alarm resolve. I have one recording system/device which can sent alarm for every fault in system via trap.
    After receive trap NetXMS is configure to create alarm with some serial number. Unfortunately, recording device can't sent trap when system itself clear all active alarms.
    Only way what I can do is auto resolving alarm when I got result 0 from reading DCI parameter "Active alarm" from this node using regular expression for all alarm of this node.
    There is one problem. NetXMS always resolve all alarms for this node no matter that some of those alarms already resolved before. In this case I have only one date for "Last changes" in alarm table for all alarms of this node.
    I don't now how filter only outstanding alarms in alarm function "Resolve all alarm with key" and regular expression. Maybe there some variable for the state of alarm (0,1,2,3 - Outstanding, acknowledged, resolved, terminated) which I can put in expressions filters.
    If anyone have some good idea please help me to resolve this situation.

    thanks in advance
    Tomislav

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

      Hi,

      that's actually looks like a bug. If alarm is already resolved system should not change it's state. We will fix it for next release.

      Best regards,
      Victor

      1 Reply Last reply
      0
      • C
        C
        CrUser
        wrote on last edited by
        #3

        Thanks you Victor.
        When you expect new revision where this bug will probably resolve?
        Tomislav

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

          Fix is already made, I plan to made release 2.2.13 within a week.

          Best regards,
          Victor

          1 Reply Last reply
          0
          • C
            C
            CrUser
            wrote on last edited by
            #5

            Thanks a lot,
            Tomislav

            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