Basically, everything zackm wrote! And I've emailed you some screenshots.
Thank you everyone for the feedback. zackm I love the detail. I wanted to check with you on point 7 you brought up:
This should allow you to specify thresholds for the UnDPs which will reflect status in an Atlas Map. In summary: Settings > Thresholds & Polling > Custom Poller Thresholds -
That's some good stuff!
Thanks for sharing, I would mention though that this is still limited to thresholds per a poller type, and not per poller.
Threshold for RemoteTemp NOT threshold for RemoteTemp on NodeA and a different threshold for RemoteTemp on NodeB
So, while this definitely addresses item 7 in my list; it also spawns a replacement.
Absolutely - I think we always have an opportunity to do better! We are certainly always trying to improve. I also had another thought around this. If the end goal is to get the Higher Level object (lets say a node) to change status, you could perform this with an alert.
Here is a general example (I used a quick UnDP I had in my lab already):
Within the alert you would need to take advantage of the Set Custom Status action:
Now, this currently only works for nodes, but you can get fancy with your Trigger Logic to get the desired result:
This will mark the node in a critical state which should draw your attention in the "map" or visual breakout.
Just a thought and something that is working for me in my lab.
Thanks again for the feedback and insight as always!
I do like this work around since critical is not normally used for node statuses it wouldn't be as confused with another condition. Still kind of a clunky process until the atlas application itself supports grabbing the value you need. In any case I think it's super important that custom sql/swql queries be supported in the same way as they are in email messages that way if people find gaps in the products in the future they can remediate it themselves rather than waiting potentially years for it to get added to the dev agenda.
designerfx Positive this lab is not Beta - Unfortunately... you seem to be also correct around the behavior here - This is likely due to the separation of UnDP data in the database. So, we are going to have to do better. For now, you would have to create individual alerts for each device. I also attempted to set the following:
Which did not appear to assist. It sounds like the separate alerts would have to be done.
Obviously not ideal, but try this and let me know if this works.
Yeah we have 200 nodes which would be impacted I could probably SWIS creation of 200 alerts based on node URI, but I don't know if I'd consider that worth the effort involved when we barely have 1 trigger/week on average.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.