Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

Home > Success Center > Log & Event Manager (LEM) > LEM Administrator's Guide > Configure LEM to store original log messages (nDepth log retention)

Configure LEM to store original log messages (nDepth log retention)

Updated: September 15, 2017

LEM can store raw (un-normalized) log messages for retention and search purposes. To enable this feature, configure the LEM Manager and the applicable connectors accordingly.
 

nDepth log retention refers to storing raw data (that is, original log messages) in a separate database. Other than the name, nDepth log retention is separate from the nDepth search engine that is available in the LEM console under Explore > nDepth.

About nDepth log retention

This section describes nDepth log retention.

Why use a separate nDepth VM?

A separate nDepth appliance provides additional capacity to store and retrieve raw log messages. If long-term storage of original log messages is a priority, then consider a separate nDepth VM. Otherwise, a separate instance is probably unnecessary. For more information contact your SolarWinds sales representative or SolarWinds Technical Support.

  • Rules do not fire on raw (non-normalized) log data. Rules can only fire on normalized data.
  • Raw (non-normalized) log messages do not appear in Monitor view in the Console.
  • If you enable original log storage (raw database storage), and you enable connectors to send data to both databases, LEM storage requirements may double for the same retention period, and extra resource reservations of at least two additional CPUs and 8-16GB of RAM may be required.

Installing a Separate nDepth Appliance or VM

In this configuration, each LEM Manager has its own dedicated nDepth appliance or VM that stores the original log files from each host (network device) and source (application or connector) that the LEM Manager monitors. You still access and explore this information using the LEM console's nDepth view even though it resides in a separate appliance or VM.

  • To use a separate nDepth appliance or VM, you must install it before you begin using nDepth. Contact SolarWinds Technical Support for instructions on installing a separate appliance.

  • If you are not using a separate appliance, this procedure is not required, because short-term log messages are stored directly on LEM.

Configuring Network Connectors for Use with nDepth

Each data-gathering connector (or, sensor connector) must be configured for use with nDepth log retention. First decide which network devices, applications, and connectors monitored by the Manager should send raw log messages to nDepth. Next, configure each of these connectors for use with nDepth. You can route connector log messages directly to LEM, directly to nDepth, or to both.

See Configure connectors to send original log data to LEM for more information.
 

SolarWinds recommends configuring each connector so it routes its log messages to both nDepth and LEM. This allows you to receive events on these connectors, and to search log messages stored on the separate nDepth instance.

Configure LEM Manager to store original log files in their own database

The following procedure must be completed prior to configuring any connector to send log messages to your LEM appliance.

  1. Open the CMC command line. See Log in to the LEM CMC command line interface for steps.

  2. At the cmc> prompt, enter manager.

  3. At the cmc::manager> prompt, enter configurendepth and follow the prompts to configure your LEM Manager to use an nDepth server:
    1. Enter y at the Enable nDepth? prompt.

    2. If you are prompted with Run nDepth locally?(Recommended), enter y. This will configure a separate database on your LEM appliance to store original log files.

    3. If your LEM implementation consists of several appliances, follow the prompts to complete the process for your dedicated database or nDepth appliance. For additional information about this process, contact Support.

  4. Back at the cmc::manager> prompt, enter exit to return to the previous prompt.

  5. At the cmc> prompt, enter ndepth.

  6. At the cmc::nDepth# prompt, enter start. This command will start the Log Message search/storage service.

  7. Enter exit to return to the previous prompt.

  8. Enter exit to log out of your LEM appliance.

Configure connectors to send original log data to LEM

  1. Open the connector for editing in the Connector Configuration window for the LEM Manager or LEM Agent, as applicable:
    • If the connector has already been configured, stop the connector by clicking gear > Stop, and then click gear > Edit.

    • If the connector has not been configured, create a new instance of the connector by clicking gear > New next to the connector you want to configure.

  2. In the Connector Details pane, change the Output value to Alert, nDepth. Leave the nDepth Host and nDepth Port values alone unless otherwise instructed by Support.

    The Output values are defined as:

    • Alert: Sending data to the alert database>

    • nDepth: Sending data to the RAW (original log) database

    For help, see The Connector Configuration form fields for data-gathering (sensor) connectors

  3. If you are finished configuring the connector, click Save.

  4. Start the connector by clicking gear > Start.

  5. Click Close to close the Connector Configuration window.

  6. Repeat these steps for each connector you want to send original log data to your LEM appliance.

View and search your original log messages

See Search raw log messages using nDepth search in LEM for details.

Last modified

Tags

Classifications

Public