Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Job Scheduler v2: Results Notified Error component incorrectly shows Warning or Critical state

Job Scheduler v2: Results Notified Error component incorrectly shows Warning or Critical state

Overview

The Job Scheduler v2: Results Notified Error component is in Warning or Critical state in the monitored Orion Server application in SAM when the application is not in any of these states.

Environment

All SAM versions

Resolution

Note: A fix has been deployed in SAM 6.0 but upgrading to the latest version does not include updating existing templates.

  1. Open the monitored application in the Orion Web Console
  2. Edit the Application Monitor from the Application Details section:EditApp.PNG
  3. From here Expand the "Job Scheduler v2: Results Notified Error" Component
  4. Find "Count Statistic as a Difference"
  5. Click "Override Template" next to it
  6. Select the checkbox to mark it as True:                                              ​​​JobSchComp1.png​​
  7. Click "Submit" to confirm the changes

Cause 

The initially-released Orion Server template that included this component did not have the Count Statistic as a Difference option enabled as a default setting.

 

This metric shows the number of failed attempts to deliver polling job results from the Job Engine v2 service to the consumer. If the result consumer is not running and active polling job results are not accepted, this number will increase. Job engine has a buffer for short-term growth that may be experienced during restart. However, this buffer is limited and permanent growth of this counter will cause permanent data from polling to be discarded and introduce gaps in historical data.

 

 

Last modified

Tags

Classifications

Public