Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > LEM monitored via NPM

LEM monitored via NPM

Updated: January 18th, 2017

Overview

This article details information on monitoring older versions of LEM using NPM.

Environment

LEM versions prior to 6.3.1

Detail

Prior to LEM 6.3.1, it was not a feature of LEM that it could be added into NPM for monitoring via SNMP. It could only be added as an ICMP node. As an alternative, it was suggested to monitoring the VM itself.

Please keep in mind, LEM has internal monitoring, it makes sure that the logs/data is not going above 90%. If there are any issues with space, then internal warnings, and emails may be triggered.

If you review Rules, you will find that there are out of the box rules that are for monitoring LEM. If they are not enabled yet, you can then enable those which are required, adjusting and tailoring to your requirements.

 

LEM 6.3.1 onwards allows LEM to be polled via SNMPv3, please see Set up SNMP monitoring in the Orion Web Console for details to enable this.

For more details on the changes in LEM 6.3.1 please see the release notes here.

 

 

 

 

Last modified

Tags

Classifications

Public