Submit a ticketCall us
Home > Success Center > Log & Event Manager (LEM) > LEM - Knowledgebase Articles > nDepth searches are slow or return a timeout error before finishing

nDepth searches are slow or return a timeout error before finishing

Created by Justin Rouviere, last modified by MindTouch on Jun 23, 2016

Views: 1,961 Votes: 4 Revisions: 7


Your nDepth queries have slow performance and take abnormally long to finish. Or instead of finishing and returning results, you get no events returned and a timeout error above the graph.


All LEM versions


Increase the timeout

  1. Log into the LEM Web Console as an Admin user.
  2. Click Manage > Appliances.
  3. Under Properties go to the Settings tab.
  4. Locate Connection Requests and increase the timeout to the preferred limit.
    Note: The maximum limit is 30 minutes.
  5. Click Save.

Decrease search complexity

The searches can complete before it times out by reducing the complexity of the search. For example, searching for a one week time frame instead of a month's time frame may complete within the timeout window.


  • The Log and Event Manager keeps one week of data in an unzipped state.
  • Data older than one week is compressed to save on disk space to allow to store more data and searching through this data takes extra time.

Increase resources

LEM uses CPU cycles and RAM to search the database. SolarWinds recommends to increase the LEM resources by an additional 2 Cores and 8 GB of RAM to improve performance and accelerate search query results.



Last modified