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. Suspect that my deactivation event doesn't register in event log

Suspect that my deactivation event doesn't register in event log

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

    Hi,

    I am trying to make a custom event and custom event processing policy to generate alarm for Percentage of disk usage, but I cannot make the alarms auto-terminate when the disk usage goes under the threshold.

    When I keep the default SYS_THRESHOLD_REARMED in data collection configuration -> threshold -> Deactivation event I can see it in the event log so I suspect my custom event.

    Is there any way I investigate this further?

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

      Hi,

      what alarm keys you are using for alarm creation and termination?

      Best regards,
      Victor

      1 Reply Last reply
      0
      • J
        J
        JhnPrfct
        wrote on last edited by
        #3

        Hi,

        I use the same key to create the alarm as I do to terminate, I think this should be fine

        I suspect that it might be working, one node raised an alarm... But I think the original one doesn't still (need to confirm when I'm at the office). I had modified the thresholds on both the node and the template multiple times, so I'm not sure if it was some kind of hickup somewhere.


        alarm_key.PNG

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

          Hi,

          policy looks correct, maybe problem is with your thresholds. Can you share threshold configuration please?

          Best regards,
          Victor

          1 Reply Last reply
          0
          • J
            J
            JhnPrfct
            wrote on last edited by
            #5

            Hi,

            I have re-created the situation now, see attachments, but basically,

            I create a warning-evert and a normal-event
            I create an event processing policy
            I set the threshold on the node DCI
            The warning threshold is triggerd, the event registers in the event log
            The alarm appears
            I set the threshold value to a higher than the actual value to trigger a normal-event
            No event in event log
            The alarm is still visible
            But, the DCI is OK in Last values view

            BR,
            John


            eventlog.PNG

            epp.PNG

            thresholds.PNG

            alarms.PNG

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

              Yes, this is tricky part - you cannot test threshold by changing it. When you edit threshold internally it leads to deleting old one and adding new one - and new threshold do not have "activated" state, so no deactivation event. For testing thresholds you can use transformation script on DCI which you can change to return value above or below threshold.

              Best regards,
              Victor

              1 Reply Last reply
              0
              • J
                J
                JhnPrfct
                wrote on last edited by
                #7

                Hi Victor,

                I assume you are sure about this as lead developer and I will mark this as resolved. But, I'm sure that I just now adjusted a threshold to be over the last value and the alarm disappeared, I guess it's some other mechanic I see.

                I'll use DCI transformation to adjust my values instead of the threshold 🙂

                Thanks,
                John

                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