Performance Data Archiving

Performance Data Archiving

Which are the database tables to be queried for performance data?

Here are the details that might help you extract reports by connecting to the database:

1. The resources polled for data collection are stored in the table polleddata, and each polled data is assigned an ID. The name of the device in which these resources are polled is stored in the AGENT field. The following query will list the resource name (which is the polled-data), the resource id, and the agent (device) name:
select name,id,agent from polleddata;

2. The data collected on polling these resources is stored in the STATSDATA tables. The data is periodically archived for easy reporting and maintenance. The value of ID field in polleddata is stored as POLLID in the STATSDATA table. So, for a given device, the data collected for a particular resource can be retrieved using the following query assuming, the POLLID is 413:
select * from statsdata6_17_2006 where pollid=413;

3. The data archiving is something like this:
All the collected raw data is in a table called STATSDATA<MM-dd-YY>. Assume the data collection interval is 15 mins. So, in an hour, there are 4 values collected. Once every hour, these 4 values are \\averaged\' to one value in STATSDATA_HOURLY table. Every day, the values in the STATSDATA_HOURLY table are averaged to the STATSDATA_DAILY table.

The data in the raw table, i.e., STATSDATA table, is maintained for 7 days by default and can be icremented to a max of 15 days. In _HOURLY table, the data is maintained for 30 days by default, and can be incremented to 90 days max. Similarly, the data in the _DAILY table is maintained for 365 days, and can be pushed upto 3650 days max. This maintenance can be configured from Admin-->Database Maintenance option.

                    New to ADSelfService Plus?

                      • Related Articles

                      • Details of tables storing performance data in OpManager

                        Details of tables: The performance data tables in OpManager 7 and above are quite distributed, enabling better reporting. Here is a quick summary of the tables that you will need to take custom reports 1. ElementsAvailabilityHourly - Every day device ...
                      • Creating performance monitors

                      • Data Collection Manager

                      • Data collection problem in the Linux setup

                        Issue: Data won't be collecting in OpManager. Cause: Data scheduler is been stopped as Opmanager unable to get the IP. Fix: Check if the device IP address present in the /etc/hosts file. If not, add the entry with the device name and restart the ...
                      • Alarms for "Data Not Collected" monitors

                        1.Please edit the NmsProcessesBE.conf file in OpManager\conf folder and search for the text CLEAN_DATA_INTERVAL 999999 . 2.Paste GENERATE_DATACOLL_EVENT true right after that. For example : CLEAN_DATA_INTERVAL 999999 GENERATE_DATACOLL_EVENT true ...