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

S

spiazza

@spiazza
Unfollow Follow
About
Posts
3
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Using filtering script in event processing policy to send single email
    S spiazza
    Support

    I am using netxms version 1.2.13 are there any limitations I should be aware of? It could be an error on my part, but it seems like I am unable to create a persistent storage variable within the filtering script. Every time the alarm triggers the script runs fresh with no memory of the defined variables from the previous trigger. I see in the version 2.2 admin guide there is a "persistent storage" view within the "configuration" drop down and this version 1.2.13 does not have a "persistent storage" view.

    As a test I entered the below code in the filtering script. The result was the action was never triggered. How can I make x persistent?

    if ( x != "" ) return false;
    x=1;
    return true;
    

    On the hyperlink you shared it says FindAlarmByKey is since version 2.0? Let me know if I just need to upgrade!


  • Using filtering script in event processing policy to send single email
    S spiazza
    Support

    Tursiops, thank you for the response.

    The method you're describing certainly seems like it would work for my situation. Could you please share some of your commands/syntax used to create and increment the persistent storage variable? I am new to netxms scripting and am not sure how to create a script to do this


  • Using filtering script in event processing policy to send single email
    S spiazza
    Support

    Hello,

    My company uses netxms to monitor BGP connections in WAN circuits and I would like to set up an automated email when a circuit goes down.

    Our monitoring is set up so the alert count increments every hour while the circuit is down, so the email alert sends every time the alert increments.

    I would like to set this up so the email only sends on the original alert and does not send as the alert continues to increment.

    I was hoping to add a filtering script to the alert so that it only sends when the counter = 1, but I do not know what the proper syntax is or if that is even possible. I'm also open to other suggestions on how to accomplish this, thank you!


    alert ex.PNG

    circuit down alert ex.PNG

  • 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