Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > Diskusage command output description

Diskusage command output description

Updated January 24, 2018

Overview

 

This article describes the values that display when you run the diskusage command in a PuTTY session with LEM or on a Microsoft® Hyper-V® or VMware® Vsphere® virtual machine hosting LEM. 

Environment

  • All LEM versions

Detail

Below is the output that displays after you run the diskusage command on a Hyper-V or vSphere console hosting LEM or in a PuTTY session with LEM:

     cmc::appliance > diskusage
     Checking Disk Usage (this could take a moment)... ....oo.oo.oo.oo.
     Partition Disk Usage:
             LEM:             46% (1.3G/2.9G)
             OS:              60% (1.7G/2.9G)
             Logs/Data:       28% (60G/230G)
             Temp:             3% (130M/5.8G)
     Database Queue(s): 4.0K (No alerts queued, 5 alerts waiting in memory)
     Rules Queue: 2.1M (0 alerts queued, 0 alerts waiting in memory)
     Console Queue: 2.1M (0 alerts queued, 0 alerts waiting in memory)
     EPIC Rules Queue: 2.1M (0 alerts queued, 0 alerts waiting in memory)
     Logs: 178M

The following sections describe the values that display in the diskusage output.

Partition Information

Partition Description
LEM The file system containing the LEM application. This value should range from 40 to 70%.
OS The file system containing the operating system. This value should range from 40 to 70%.
Logs/Data

The file system containing the database and the 'temporary' syslog.

Log data uses up to 90% by default, but can configure to use up to 98%)

Temp The LEM application uses 5% of /tmp by default. Contact Support if this value is higher than 10%.

Additional Information

Item Description
Database Queue(s)

The queue system for alerts sent to the database.

After being fed from the Rules queue, data continues to the respective targets, including the Database queue. 

Only the alerts waiting in memory will vary from 0 to 100,000 without being a concern.

Rules Queue Corresponds to alert distribution policy, the channeling of alerts from the manager to the respective distribution channels, including Console, DB, Rules, and Warehouse (present, but no longer used). 
Console Queue

The queue system for the consoles connected to the manager.

After being fed from the Rules queue, data continues to the respective targets, including the Console queue. The Console on the client-side can back up as well to avoid a situation where everyone's Console is blocked by one Console that can't keep up.

EPIC Rules Queue

The queue system for the correlation engine.

After being fed from the Rules queue, data continues to the respective targets, including the EPIC or New Rules queue.

Logs

The storage space used by syslog. If larger than 30GB, contact Support for assistance to manage the storage space size. 

Normally, all queues values are 0 or no alerts, except for the database alerts waiting in memory.

LEM size

The LEM size can vary from 250GB (default) up to 2.0TB (when increased in LEM 6.3.1). The operating system applications and temporary storage (such as caching and paging) use around 20GB, providing syslog uses a minimal amount. The remainder is used for the database. Resizing the LEM accommodates the retention period (timespan in days value).

Run the Database Maintenance Report from the LEM Reports application to view the timespan in days value.

 

 

 

Last modified

Tags

This page has no custom tags.

Classifications

Public