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 > Network Performance Monitor (NPM) > Network object is missing from the Network Object menu on the Syslog page

Network object is missing from the Network Object menu on the Syslog page

Table of contents
Created by Ezgi Muderrisoglu, last modified by MindTouch on Jun 23, 2016

Views: 1,365 Votes: 0 Revisions: 4

Overview

This article discusses why a network object does not appear in the menu of choices when looking for syslogs.

Environment

NPM 11.5.2

Detail

A device will not appear in the Network Objects menu if NPM has not received syslogs from this device. This can be confirmed by running a SQL query on the Syslog's table from the database manager. There will be no entries in the table from the Network Object in question.

If you were expecting syslog messages from the device then there may be an issue with either:

  • Verify that the device is sending the syslog messages.
  • Check NPM settings to verify that all credentials are correct for syslog messages to be correctly received correctly by NPM. 
  • Check retention settings and verify that the syslogs sent fall within the retention period. For example, the retention period is seven days. If the syslogs stopped sending on the seventh day, and the syslog page was then checked on the eighth day, then there would be no device in the list.
  • If the monitored node is monitored by Agent based polling, you may need to do the following:
    • Open: C:\Program Files (x86)\SolarWinds\Orion\SyslogService.exe.config
    • Find the line:
    • <add key="CutOffAgentNodes" value="true"/>
    • And change true to false. Restart the Syslog service.

 

Last modified

Tags

Classifications

Public