Data Retention in Applications Manager
Attribute data
Polled data
This comprises of the data collected for the attributes in each poll of the monitor.
This data is used to generate Polled Data report, which can be accessed by clicking on the value of the required attribute and selecting Show Polled Data from the custom time period dropdown from the monitor page.
For server monitors, custom monitors, and other monitors like DB2, the default retention period for this data is 5 hours, which can be altered by specifying the required value for the option Raw data cleanuptime (hours) under Settings -> Server Settings.
For remaining monitors, the default retention period for this data is 30 days, which can be altered by specifying the required value for the option Conf data cleanup interval (days) under Settings -> Server Settings.
Archived Data
This comprises of the polled data archived as daily and hourly averages in Applications Manager. This data will be archived only if the reports are enabled for the required attributes under Settings -> Enable Reports.
This data is used to generate all attribute-based reports, At a glance report, etc. for all the monitors from the Reports tab.
The default retention period for daily archived data is 365 days, which can be altered by specifying the required value for the option Daily statistics will be maintained for the last __ days under Settings -> Data Retention.
The default retention period for hourly archived data is 90 days, which can be altered by specifying the required value for the option Hourly statistics will be maintained for the last __ days option under Settings -> Data Retention.
For Servlet and disk IO related attributes, hourly average data is retained for the last 30 days, by default. This can be modified by specifying the required value for the option Disk and servlet attributes will be maintained for the last __ days under Settings -> Data Retention -> Advanced Settings.
Availability Data
This comprises of the availability history data of monitors and monitor groups stored in Applications Manager.
This data is used to generate all the Availability reports and Availability history data related widgets.
We do not clean up the availability data, by default. However, users can configure the data retention period for availability data by specifying the required value for the option Clean Downtime History before __ days under Settings -> Data Retention -> Advanced Settings.
Health History
This comprises of the health history data (the time interval when the resource's health is in 'Critical' state) of monitors and monitor groups stored in Applications Manager.
This data is used to generate all the Health History report from the Reports tab.
The default retention period for this data is 365 days, which can be altered by specifying the required value for the option Clean Health history before __ days under Settings -> Data Retention -> Advanced Settings.
Health Percentage Data
This comprises of the Health percentage data (i.e. the clear, critical and warning state percentage) of monitors and monitor groups.
The default retention period for this data is 365 days.
Attribute archival data retention configuration applies for this too.
Event count data
This data comprises of the Event counts (i.e., the number of times the critical/ clear/warning events occurred) of monitors and monitor groups stored in Applications Manager.
This data is used to generate Alarms Summary report for Monitor Group from the Reports tab.
The default retention period for this data is 365 days, which can be altered by specifying the required value for the option Clean Event count before __ days under Settings -> Data Retention -> Advanced Settings.
Event data
This comprises of the Alarm History data along with RCA messages of monitors and monitor groups stored in Applications Manager.
This data is used to generate Alarm History data shown in the Alarms tab and upon clicking the Alarm History option from the Monitor and Monitor Group page.
The default retention period for this data is 30 days.
New to ADSelfService Plus?
Related Articles
How data is collected in Applications Manager for IBM WebSphere Application Server?
In Applications Manager, we generally support monitoring for versions 5.x to 9.x, and data collection for each version may differ based on the version of the IBM WebSphere Application Server being monitored. For versions 6.x to 8.x - Data collection ...Authentication Methods in Applications Manager
Authentication involves validating an incoming user to facilitate the access to a specific resource. There are various authentication methods that you can use - based on the requirements and usage. In recent times, numerous organizations are ...APM Insight monitor is UP, but monitor page doesn't show any data
Possible Causes The APM Insight monitor status corresponds to the respective agent folder pointed Java Application status i.e., as long as the Application server is running, the monitor status will be UP. 1. No Transactions Recorded: It is possible ...Monitoring Capacity Entitlement in Applications Manager
Applications Manager is equipped to monitor processor capacity entitlement issues. To measure the average entitlement value during peak production times with a higher workload, you can use the following command: lparstat 1 20 > /tmp/apm_physc.txt && ...Applications Manager is not collecting data from Tomcat Server.
If the proxy settings are configured wrong, then Tomcat Data collection will not happen correctly as Applications Manager uses HTTP requests for data collection from Tomcat Server. Check if you are able to access the Tomcat Server from browser in ...