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

Is there a SAM Report to report values when Critical?

I know, the title is vague....

I am monitoring a SQL database server with the SQL Server 2005-2008 Performance (WMI)” template. I see in Node Details under Event Summary and click on "SAM Critical" there are a lot of events. I am trying to compile a report of what the values were when the SAM went Critical.

When I click on the hyperlink it simply takes me to the current information which makes it impossible to see what trigger the Critical.

Is there a way to generate a report for the SAM Component values when it trips to Critical?

Sample:

4/1/2015 1:19 PM Application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

4/1/2015 1:19 PM Component "Memory: Pages/sec" for application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

4/1/2015 12:54 PM Application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

4/1/2015 12:54 PM Component "Buffer Manager: Page writes/sec" for application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

4/1/2015 12:54 PM Component "Buffer Manager: Page reads/sec" for application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

4/1/2015 5:02 AM Application "Windows Server 2003-2012 Services and Counters" on node "<server>" is in a critical state

4/1/2015 5:02 AM Component "% Processor Time" for application "Windows Server 2003-2012 Services and Counters" on node "<server>" is in a critical state

4/1/2015 12:54 AM Application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

4/1/2015 12:54 AM Component "Memory: Pages/sec" for application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

4/1/2015 12:52 AM Application "Windows Server 2003-2012 Services and Counters" on node "<server>" is in a critical state

4/1/2015 12:52 AM Component "Pages/sec" for application "Windows Server 2003-2012 Services and Counters" on node "<server>" is in a critical state

4/1/2015 12:52 AM Component "% Processor Time" for application "Windows Server 2003-2012 Services and Counters" on node "<server>" is in a critical state

3/31/2015 10:47 PM Application "Windows Server 2003-2012 Services and Counters" on node "<server>" is in a critical state

3/31/2015 10:47 PM Component "Pages/sec" for application "Windows Server 2003-2012 Services and Counters" on node "<server>" is in a critical state

3/31/2015 10:24 PM Application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

3/31/2015 10:24 PM Component "Locks: Lock Timeouts/sec" for application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

3/31/2015 8:59 PM Application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

3/31/2015 8:59 PM Component "Buffer Manager: Page writes/sec" for application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

3/31/2015 7:54 PM Application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

3/31/2015 7:54 PM Component "Memory: Pages/sec" for application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

3/31/2015 7:34 PM Application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

3/31/2015 7:34 PM Component "Memory: Pages/sec" for application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

3/31/2015 7:27 PM Application "Windows Server 2003-2012 Services and Counters" on node "<server>" is in a critical state

3/31/2015 7:27 PM Component "Pages/sec" for application "Windows Server 2003-2012 Services and Counters" on node "<server>" is in a critical state

3/31/2015 4:47 PM Application "Windows Server 2003-2012 Services and Counters" on node "<server>" is in a critical state

3/31/2015 4:47 PM Component "Pages/sec" for application "Windows Server 2003-2012 Services and Counters" on node "<server>" is in a critical state

3/31/2015 3:49 PM Application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

3/31/2015 3:49 PM Component "Memory: Pages/sec" for application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

3/31/2015 3:47 PM Application "Windows Server 2003-2012 Services and Counters" on node "<server>" is in a critical state

3/31/2015 3:47 PM Component "Pages/sec" for application "Windows Server 2003-2012 Services and Counters" on node "<server>" is in a critical state

3/31/2015 3:39 PM Component "Locks: Average Wait Time (ms)" for application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

3/31/2015 3:39 PM Component "Locks: Lock Waits/sec" for application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

3/31/2015 3:34 PM Application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

3/31/2015 3:34 PM Component "Memory: Pages/sec" for application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

3/31/2015 3:32 PM Application "Windows Server 2003-2012 Services and Counters" on node "<server>" is in a critical state

3/31/2015 3:32 PM Component "Pages/sec" for application "Windows Server 2003-2012 Services and Counters" on node "<server>" is in a critical state

3/31/2015 3:32 PM Component "% Processor Time" for application "Windows Server 2003-2012 Services and Counters" on node "<server>" is in a critical state

3/31/2015 3:24 PM Application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

3/31/2015 3:24 PM Component "Locks: Lock Timeouts/sec" for application "SQL Server 2005-2008 Performance (WMI)" on node "<server>" is in a critical state

Find more posts tagged with

Accepted answers

All comments

silverbacksays

Have a look at the events view. If you filter it for the node in question, you should see the value of the particular application monitor when it went first to warning, then critical.

FormerMember

Silverback... nope, looks like the same results from the Events tab as in the application summary. It tells me what part failed but not the value at the time of failure. I need to be able to see the value that breached the threshold.

silverbacksays

Curses! Whelp, I'm sure someone more enlightened that I will come up with a solution for you. Have a nose around the content exchange for SAM if you haven't already while you wait, there may be something in there you can jury rig to give you a solution.

Failing that, log a support call

Oh, one other thing occurs to me: If you know the component, you could click on the relevant resource of that component to see the graph of the polled stats. Adjust the times to cover the period of the problem and then click 'view chart data'. The polled stats are timestamped in there, so it should give you a date/time and a value.

Not very elegant, but maybe that will serve as a stopgap.

aLTeReGo

Clicking on the message in the Event for a component that has gone into a warning or critical state should take you to the Component Details view where you will see a chart showing the statistical values over time in relation to their warning or critical threshold. This allows you to easily see when a threshold was crossed and what the value was at that time.

Chat Thresholds.png

If you want this information in the Event, you can configure the Alert Action in the Advanced Alert Manager to write an event that includes the current value at the time the component was in Warning or Critical, as well as what the warning and critical threshold is for that component. These are all macro variables that are available via the Alert Manager for use in email notifications, as well as writing events to the Orion event log.