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 availability reports are taken from this table.
2. ElementsAvailabilityDaily- This table is queTried for availability reports for over a week. Has data archived every 24 hours.
3. IfRaw_<date> - This table has data of interface traffic, errors, discards etc
4. IfHourly_<date> - This has values archived every one hour for all the interface data
5. IfDaily_<date>- This has values archived every 24 hours
OpManager archives the above performance tables after the row-count exceeds apprx 250,000 rows. So, to know the date of the table to be queried, query the table METATABLE. This lists all the perforformance tables. The current performance tables (the names of which are mentioned above) will have the value as -1 for ENDTIME field.
Each element/device is a managed object and has a unique ID, which you can retrieve using MOID field in the ManagedObject table. The value of this MOID is the same as ElementID field in the above tables. So, you can use a join between these two tables to create custom reports.
Besides the above tables, the host resources data such as that of CPU, Memory etc are persisted in the following table:
1. Statsdata<current date>: This stores the current or raw data. That is, the data as and when collected. This table is created every 24 hours. New table is created at 12.00 midnight.
2. Statsdata_hourly: Which has values archived every one hour. Hourly data is stored for a period of 15 days by default and can be set to a maximum of 90 days.
3. Statsdata_daily: Which as values archived every 24 hours. Daily data is stored for a default period of 1 year and can be set to store for a max of 10 years.
For additional information refer to DatabaseSchema.conf located under OpManager/conf folder
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 availability reports are taken from this table.
2. ElementsAvailabilityDaily- This table is queTried for availability reports for over a week. Has data archived every 24 hours.
3. IfRaw_<date> - This table has data of interface traffic, errors, discards etc
4. IfHourly_<date> - This has values archived every one hour for all the interface data
5. IfDaily_<date>- This has values archived every 24 hours
OpManager archives the above performance tables after the row-count exceeds apprx 250,000 rows. So, to know the date of the table to be queried, query the table METATABLE. This lists all the perforformance tables. The current performance tables (the names of which are mentioned above) will have the value as -1 for ENDTIME field.
Each element/device is a managed object and has a unique ID, which you can retrieve using MOID field in the ManagedObject table. The value of this MOID is the same as ElementID field in the above tables. So, you can use a join between these two tables to create custom reports.
Besides the above tables, the host resources data such as that of CPU, Memory etc are persisted in the following table:
1. Statsdata<current date>: This stores the current or raw data. That is, the data as and when collected. This table is created every 24 hours. New table is created at 12.00 midnight.
2. Statsdata_hourly: Which has values archived every one hour. Hourly data is stored for a period of 15 days by default and can be set to a maximum of 90 days.
3. Statsdata_daily: Which as values archived every 24 hours. Daily data is stored for a default period of 1 year and can be set to store for a max of 10 years.
For additional information refer to DatabaseSchema.conf located under OpManager/conf folder
New to ADSelfService Plus?
Related Articles
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 ...OpManager Scalability recommendations
If your organization is expanding and looking to introduce additional elements and monitors, follow this guide on scalability recommendations. We've outlined the maximum counts and limits for resources and metrics in OpManager to maintain optimal ...How to remove the ServiceDeskPlus details in OpManager?
ISSUE: To remove the ServiceDeskPlus details in the Add-On settings page and from the device snapshot page. SOLUTION: We need to delete entries in the three tables in the database. 1. Connect to the database using this command, ...Vulnerabilities in OpManager 12.0
VULNERABILITY DETAILS(found in build 12000) Vulnerability 1: Unrestricted File Upload: OpManager fails to validate or improperly validates files before uploading to the system. As a result an attacker might be able to upload arbitrary JSP file and ...Discover Layer 2 Maps in OpManager.
Discovery mechanisms used in OpManager Layer 2 discovery: The following discovery mechanisms are used for discovering layer 2 devices in OpManager. ARP (Address Resolution Protocol): Maps IP addresses to physical (MAC) addresses, mainly used by Layer ...