Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Component Monitor Threshold Values Report v2

Evening Fellow Thwacksters,

I was recently on a customer site, and they were getting a lot of questions asked about the various different Warning & Critical alerts coming from SolarWinds. The customer wanted a report that he could present to his business that helped to clarify what Warning & Critical meant in real money so to speak. I knew this must be in the database, and after looking around, I was directed to this report written by aLTeReGo and modified by geoffb & ecklerwr1 .

Great I thought but hold on - Report Writer in 2019 that can't be, there must be a better way to do this! So I loaded up the trusty SWQL Studio and got to work!!!

SELECT DISTINCT
       [App].Template.Name AS [Application Template Name]
      ,[App].FullyQualifiedName AS [Application Name]
      ,[App].DetailsURL AS [App DetailsURL]
      ,[App].Status AS [App Status]
      ,[Comp].Name AS [Component Name]
      ,[Comp].DetailsURL AS [Comp DetailsURL]
      ,[Comp].Status AS [Comp Status]
      ,[Comp].ComponentOrder AS [Component Order]
      ,[tbcWarn].ThresholdName AS [Threshold Name]
      ,[tbcWarn].Warning AS [Warning Threshold]
      ,[tbcCrit].Critical AS [Critical Threshold]
FROM Orion.APM.Application AS [App]
INNER JOIN Orion.APM.Component AS [Comp]
   ON App.ApplicationID = Comp.ApplicationID
LEFT JOIN Orion.APM.ThresholdsByComponent AS [tbcWarn]
   ON Comp.ComponentID = tbcWarn.ComponentID 
  AND tbcWarn.Warning < 1.797E+300
  AND tbcWarn.Warning > -1.797E-300
LEFT JOIN Orion.APM.ThresholdsByComponent AS [tbcCrit]
   ON Comp.ComponentID = tbcCrit.ComponentID
  AND tbcCrit.Critical < 1.797E+300
  AND tbcCrit.Critical > -1.797E-300
WHERE (tbcWarn.Warning IS NOT NULL)
  AND (tbcCrit.Critical IS NOT NULL)

I would like to give thanks to zackm for getting me over the finish line with some of the query logic, and KMSigma for coming in at the end and tidying up the formatting Oh and wluther for moral support!

I was pretty pleased with the way this turned out, and I loaded it into a Report via Custom Table. I hope it helps other people, and of course, feel free to expand on it in any way. I know I want to.

I've attached the report I build just in case your feeling lazy

- David Smith (dgsmith80 )

Kenson - SolarWinds Authorised Partner

Training, Licenses & Professional Services

Component+Monitor+Threshold+Values.xml

Find more posts tagged with

Accepted answers

All comments

ecklerwr1

Nice one Dave! I still have a bunch of report writer stuff running reports.

wluther

Good stuff there, dgsmith80!

zackm

head's up; jbiggley ran across this today reviewing the release notes for our upgrade tomorrow: Orion Platform 2018.4 Release Notes - SolarWinds Worldwide, LLC. Help and Support

tl;dr - not dead yet, but the bombs are en route to blow up the old things. As this platform release came last October, I'd assume we're getting pretty short on time.

zackm

Love it; it was a lot of fun collaborating with you on this on dgsmith80!

ecklerwr1

That kinda a bummer really... my guess is some people aren't going to be very happy if stuff just stops working. This isn't the only thing that's a little frustrating... how many log managers do they have now as well? One company selling competing products is a little strange.

mesverrum

I've been warning people to migrate away from Report Writer since I first started consulting 4 years ago, can't be too big a shock that the want to stop having to support a feature that the replaced in the product that long ago.

On the logs topic it is pretty obvious that the direction the wind is blowing is that once they get all the stuff figured out with LM as an integrated product that will be dropping the built in trap/syslog viewer. Maybe it takes another 4 years for them to delete the files from the install but I'm expecting it.

dgsmith80

I agree the sooner we move away from 32bit apps the better and the vision has always been a Single Pane of Glass!

jfaldmo

What are the limitations of this report? For example, should this show every alert for every server? It isn't showing at least some of the servers where I would expect to see alerts.

I just put the query from the original post into a report. The report just showed the following metrics for my system (though there were a lot of nodes that all had these metrics, there were nearly 6000 lines--)

CPU

IIS_PageRequestsThreshold

IISBB_Sites_SslCertificate_DaysRemaining

PMem

SQLBB_Indexes_Fragmentation

StatisticData

VMem

Is that all that is expected or am I doing something wrong?

I was working on something similar and the query I came up with required using the DynamicEvidenceColumnSchema table.

dgsmith80

Hi Jon,

So this is more of an informational report. It shows you what your Warning & Critical Values are in all active components. In most cases, these are inherited by the Template but can be overridden which is why I ran it from the Monitor level. If you are alerting on Component in Warning or Critical state then this report will be able to give you at-a-glance information on what the metric was that was breached. Of course, there are ways to include that information in the alert as well.

As I said this was built for a specific customer request, which was to help educate the other members of the team getting the alerts.