Comments
-
Thank you.
-
Thanks, will be using the web based writer from now on.
-
I am running SAM 6.1.1,i will open a case with support. Also are these settings being saved in the database? If so which table? Thanks.
-
I don't think it would be possible for me to migrate the report into a web based report, as i need a specific set of data which i can only get by querying the database using my own SQL query, and creating a report from an SQL query seems to be only supported in the legacy report writer. I will probably change my report…
-
Thanks that worked.
-
i set the days for detail,hourly and daily and after i click submit and come back to check the settings it resets it back to the old settings, any ideas why this is? Edit: It only goes back to the old values when i check the settings the second time very strange
-
Thanks problem solved.
-
I tried that still didn't work, ticking that check box seems to only remove the top section of the web interface(e.g. the home tab etc) from the report.
-
Thanks for that. Looking around the database is it safe to assume that the availability of a component monitor(e.g. HTTP monitor) is found on the APM_ComponentStatus tables? I can also see the availability column in the APM_ComponentStatus table is an integer, is there reference table which details what each integer means?
-
Thanks for that found all the tables i need . The Containers table stores the groups data(e.g. group name) and the ContainerMemberSnapshots table stores the mapping between the groups and the nodes.
-
Ended up moving the database from SQL express to enterprise, needed the historical data. Thanks for you suggestions.
-
I really want to avoid using solar winds predefined templates, is it possible to create a new template with the following SQL Table Monitor called All Databases or something that has similar monitoring capabilities. One thing i find useful about this monitor is it monitors each database instance on my SQL server to see if…
-
When adding a node it seems solar winds sends a request on port 135 to the node you are trying to add, and then sends another request using some random port (in my case this random port was either 5503 or 5502). The request for port 135 went through successfully to the node i was trying to add, whilst the request for both…