Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Date format in local time in SAM is different from UTC in NPM

Date format in local time in SAM is different from UTC in NPM

Table of contents
Created by Jamin Walters, last modified by MindTouch on Jun 23, 2016

Views: 1,516 Votes: 1 Revisions: 5

Overview

This article provides information when comparing tables that are part of NPM or Orion core to tables which are also part of SAM date formats display inconsistency. NPM tables are stored in UTC date format and many of the SAM tables are stored in local time. 

Environment

  • All versions of SAM
  • All versions of NPM

Detail

When trying to compare date and time values from NPM tables to APM (SAM) tables, the NPM tables have date time values in UTC format, while APM tables are in local time. 

 

Example tables from SWQL studio would be Orion.NPM.InterfaceTraffic  and Orion.APM.HistoricalMemory. 

Currently this would be suggested as a feature request. 

For reference, see:

https://thwack.solarwinds.com/ideas/3000 

 

 

Last modified

Tags

Classifications

Public