I need to integrate information from Solar Winds in our ticketing application. When looking at the schema for alerting, I see that the two primary entities are Orion.AlertActive and Orion.AlertObjects. I'm unclear on how the ID's for these tables work though. * If I have an alert that is triggered by a particular node, clears, and then is triggered again several hours or days later, does that second instance have a new AlertActiveID in Orion.AlertActive? Because of the Acknowledge-related properties, my guess is yes, but I'd like to confirm. * If so, what about Orion.AlertObjects; does this also get a new AlertObjectID for the second AlertActiveID? My reading of the schema suggests no, that AlertObjectID stays the same for the same combination of (AlertID, EntityUri) because of the TriggeredCount and LastTriggeredDateTime properties, but I can see where maybe this is also effectively tracking the number of times the trigger conditon was met for just one AlertActive instance. Thanks for any help!

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Tracking Orion.AlertActive in Ticket Application

I need to integrate information from Solar Winds in our ticketing application. When looking at the schema for alerting, I see that the two primary entities are Orion.AlertActive and Orion.AlertObjects. I'm unclear on how the ID's for these tables work though.

If I have an alert that is triggered by a particular node, clears, and then is triggered again several hours or days later, does that second instance have a new AlertActiveID in Orion.AlertActive? Because of the Acknowledge-related properties, my guess is yes, but I'd like to confirm.
If so, what about Orion.AlertObjects; does this also get a new AlertObjectID for the second AlertActiveID? My reading of the schema suggests no, that AlertObjectID stays the same for the same combination of (AlertID, EntityUri) because of the TriggeredCount and LastTriggeredDateTime properties, but I can see where maybe this is also effectively tracking the number of times the trigger conditon was met for just one AlertActive instance.

Thanks for any help!

Find more posts tagged with

Accepted answers

mrxinu

Hey there,

You're spot on in both instances. You get a new AlertActiveID for each new alert that triggers and the AlertObjectID gets reused for every alert configuration + entity combination.

All comments

mrxinu

Hey there,

You're spot on in both instances. You get a new AlertActiveID for each new alert that triggers and the AlertObjectID gets reused for every alert configuration + entity combination.

cmbergin

Thank you. Trying to figure all this out from just the schema is a little tricky, especially when the platform we're (potentially) coming from uses the same terms as Solar Winds but for different concepts.

mrxinu

Totally understandable. The folks with the mileage are here to help though so there's that.