I recently had to come up with a way to show what Groups a node was a member, and display this on the Node Details page. I put together a video with how this can be done using a slightly modified canned report.
Andrew LaGrone
Loop1 Systems, Inc
I recently had to come up with a way to show what Groups a node was a member, and display this on the Node Details page. I put together a video with how this can be done using a slightly modified canned report.
Andrew LaGrone
Loop1 Systems, Inc
Thanks for the video lag. I encounter a problem when I execute the query in Report Writer if the Where statement is not commented out (get a SQL error) and of course, the report does not display properly on the website.
What could be going on? My SQL looks exactly like yours.
There's a bit of a trick to it. In Report Writer, to validate the query works, you will leave the where clause commented out. Once you're ready to deploy, remove the comment. The report writer will no longer be able to run the report, but it should work in the web console now.
A good way to have this work in a report is to create a stored procedure that just returns the "table" of info. the report would then call the stored procedure. This is a good way to run reports that have case statements, if/else, and other TSQL commands that SW doesn't translate
Do you mean placing a similar report on an application summary page? I'm sure you could with some minor tweaking. Just guessing, but I bet you could replace the 'WHERE NODEID=${NodeID}" with something like WHERE ApplicationID=${ApplicationID}." Although, the convention might be off a bit, the procedure should work.
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.