Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > How to set SolarWinds Agent logs to debug if the Web transaction gets stuck

How to set SolarWinds Agent logs to debug if the Web transaction gets stuck

Table of contents

Updated: 4-6-2017

Overview

When setting a SolarWinds Agent (for Windows or for Linux) logs to DEBUG from INFO (default), the website may hang and not save the change. If this occurs, you can manually change the logging type (DEBUG) on the target agent by remote access and editing a configuration file. See Steps to resolve.

The following images displays the Edit Agent Settings page. This page may hang when changing the drop-down under Troubleshooting and saving: /Orion/AgentManagement/Admin/EditAgent.aspx

 

Environment

  • NPM 12, NPM 12.0.1, NPM 12.1
  • SolarWinds agents

Steps

To resolve, you need to remote access the server/system with the target agent (RDP).

  1. Navigate to this path: C:\Program Files (x86)\SolarWinds\Agent\
  2. Find the SolarWinds.Agent.Service.exe CFG file and edit it in Notepad.
  3. Find the tags: <logging> </logging> 
  4. In these tags, locate the <level></level> tags and replace the default value INFO with DEBUG.
  5. Save the file changes.

 

To verify the change worked:

  1. Navigate to C:\ProgramData\Solarwinds\Logs\Agent\
  2. Open any of the Discovery Plugin logs or the Agent Service EXE logs. 
  3. You should now see the logging level is inflated to DEBUG.

 

 

Last modified

Tags

Classifications

Public