My understanding is that it is safe to update Custom Properties (Node, Volume & Interface) directly through SQL, is this accurate?
Custom properties are represented by columns in given table and also by metadata stored in Information Service. If you add your own column we will have no information about them. It can later caused some issues (e.g. during upgrade) etc.
What about doing the following:
create a table and call it "MyAPMTemplateCustomProperties"
then write alerts / reports in sql referencing the extra table for my custom properties.
This could then be extended to :
?
I have already done something similar by adding an export from a CMDB as a separate table and then using writing sql to generate a report that shows the difference between the two tables.
Chris
It sounds reasonably. Of course Orion doesn't know anything about your tables so if you add any new Orion entity (let's say Group) there will be no corresponding record in your table etc.
But if you write your SQL queries carefully there should be no problem.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.