Comments
-
If anyone is reading this from the future, our eventual solution took the following form: 1. A Python script that queries our installation's database through the Orion SDK. It retrieves all the information about our nodes that we need or want to show for the map (Lat/Lng, Name, Supplier, etc.). It is hosted on Amazon as a…
-
I created a ticket for Technical Support. They basically said there is no build-in solution for our purposes and have used this thread as a feature request for the development team. We are currently investigating the possibilities of using another application to create the maps and then porting them in through the custom…
-
Just had the same issue. Found out after 6 days. Followed the fix posted by stevewright. New messages now appearing in the Audit Log again, but no historic data from the last 6 days.
-
Solarwinds support pointed me in the direction of Custom Charts. They give you better ability to customize the chart's appearance. Using the Average Response Time and the Availability data series under Response Time History allowed me to basically recreate the default Availability and Response Time chart, but now with…
-
In line 6 you only need to pass the uri, not append with /Nodes. Like so: new_name = 'Apples' swis.update(uri, Caption=new_name) The uri you get from your query is like a direct address to the node. To change things like IP, caption, EngineID, etc. you don't have to append it with anything. Only thing I've come across is…
-
I'm not familiar with this verb in particular, but it sounds like the way nodes in general behave when you create them through script but don't add pollers to them. You could verify if that's the case or not.
-
When viewing the Node itself, take a look at the top of the Custom Properties widget. If you press "Edit" there, you get a list off all custom properties (for nodes) you have. Each item in the list that has the box checked in front of it is shown in the widget. Most likely your newly added custom properties simply aren't…
