Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Understanding the behavior and usage of Orion database tables

Understanding the behavior and usage of Orion database tables

Table of contents
Created by Michael Almadova, last modified by MindTouch on Jun 23, 2016

Views: 269 Votes: 1 Revisions: 3

Overview

 

Understanding the behavior and usage of the following three tables in

the Orion-Database:

a) InterfaceTraffic_Daily

b) InterfaceTraffic_Detail

c) InterfaceTraffic_Hourly

Environment

  • NPM 11.5.2

Detail

 

The 3 tables have data based on your data retention settings.  If you keep detailed statistics for 7 days after database maintenance runs nightly it will copy any data over 7 days old in the Detail table to the Hourly table. Lets say you keep hourly data for 14 days.  During DB maintenance, the hourly data over 14 days will be summarized to daily and so on. Your detail table will have data up to the current date of collection. The rest of the tables will have data based on your retention settings.

 

Polling Settings:

 

http://www.solarwinds.com/documentat...ight=Retention settings

 

 

Last modified
22:04, 22 Jun 2016

Tags

Classifications

Public