When focused on anticipating, troubleshooting, and preventing poor user experience, the most current environment data is the most important. To ensure you have the data you need to troubleshoot user experience issues, Goliath recommends you keep at least 30 days of data.
How GPM Manages Data Retention
GPM manages data retention through a database Auto Purge feature, which can be set to run at a particular time each day. Depending on the metric or object, you can retain data up to a specific number of days as detailed below.
The following metrics can be stored up to 180 days (this duration may negatively impact product performance and is not recommended with out the infrastructure to support):
- XA/XD/Horizon (Session & Performance Metrics)
- Server Metrics (Hypervisor Host/VM/Storage Metrics)
- Counter Watch (Windows Perfmon monitoring rule data)
- Server Watch (PING, AGENT, Hypervisor Availability monitoring rule data)
- Event Log Watch (Windows Event Log Data)
- Syslog Watch (Syslog Message Data)
- All Other monitoring data (File monitoring rule data, GAAM, any item not included above)
Non-metric data retention:
- Report Files (up to 550 days)
- Sever Log files (up to 60 days)
- VMware Hypervisor Obsolete Inventory (up to 550 days)
- XenServer Hypervisor Obsolete Inventory (up to 550 days)
WARNING: Keeping large amount of data will degrade overall product performance (e.g. storing data, reporting, screens)
To access the Auto Purge feature
The Auto Purge feature is accessed by going to Settings > Database Maintenance. The Database Maintenance dialog is displayed below.