Chapter 24. Storing Monitoring Data
- Raw metrics are collected every few minutes and are aggregated in a rolling average in one-hour windows to produce minimum, average, and maximum values.
- One-hour values are combined and averaged in six-hour periods.
- Six-hour periods are combined and aggregated into 24-hour (1 day) windows.
24.1. Changing Storage Lengths for Monitoring Data
24.1.1. Default Storage Lengths
Table 24.1. Storage Times for Data
|Data||Length of Time||Configurable or Hardcoded||SQL or NoSQL Database|
|Raw measurements||7 days||Hardcoded||NoSQL|
|1-hour aggregate||14 days||Hardcoded||NoSQL|
|6-hour aggregate||31 days||Hardcoded||NoSQL|
|24-hour aggregate||365 days||Hardcoded||NoSQL|
|Availability data||365 days||Configurable||SQL|
|Events data||14 days||Configurable||SQL|
|Response-time metrics||31 days||Configurable||SQL|
24.1.2. Changing the Storage Times for Different Monitoring Data
- In the Configuration menu, select the System Settings item.
- Scroll to the Data Manager Configuration Properties section.
- Change the storage times for the different types of monitoring data.There are four settings that relate directly to storing monitoring data:
- Response time data for web servers and EJB resources. This is kept for one month (31 days) by default.
- Events information, meaning all of the log files generated by the agent for the resource. The default storage time for event logs is two weeks.
- Traits for resources. The default time is one year (365 days).
- Availability information. The default time is one year (365 days).