Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Archive > 2017December19 - Deletes > InsertionTime and DetectionTime field values are not identical in LEM

InsertionTime and DetectionTime field values are not identical in LEM

Created by Jason Dee, last modified by Jessica Solis on Dec 19, 2017

Views: 635 Votes: 1 Revisions: 8

Updated April 22, 2016

Overview

This article describes why the InsertionTime field value may vary from the DetectionTime field. These fields appear in the Event Details box when you click an event in the Monitor view. 

Environment

All LEM versions

Cause 

  • The LEM and the node sending those events are in different time zones.
  • The LEM time or time zone is not correct.
  • The source of the event has an inaccurate time or time zone.
  • Performance issues may cause the LEM to fall behind so it is no longer real time.

If your source host is located outside the LEM time zone, the time delay between the InsertionTime and DetectionTime is expected.

Resolution

  1. Ensure that your LEM appliance is configured with the correct date, time, and time zone.

    See Adjust the time, date and time zone for virtual appliance.

  2. Verify the source is configured with the correct date, time, and time zone. 
  3. If your LEM is not responding in a timely manner, verify that you have the required resources reserved for your environment.

    See Allocating resources with reservations

 

 

 

 

Last modified

Tags

Classifications

Public