Data Retention for Entities

TBD: Link to section in concepts regarding entities

This page summarizes the data retention for Cisco Cloud Observability entities. In Cisco Cloud Observability, data retention is defined by two parameters:

• Retention time-to-live (TTL): The amount of time that an entity and its data remains in Cisco Cloud Observability after the entity becomes inactive. An entity is considered inactive when its retention TTL period ends. When the purge TTL period ends, the entity data and entity-centric page is removed from the system (purged). 
• Purge time-to-live (TTL): The amount of time that an entity is considered active in Cisco Cloud Observability after it stops reporting metrics, events, logs, and traces (MELT) data. When the retention TTL period ends, the entity is considered inactive and will no longer appear in the user interface or in queries for active entities.

Cloud and Infrastructure Entities

This category includes Amazon Web Services, Microsoft Azure, Google Cloud Platform, Kafka, Redis, and Host Monitoring entities.

For all cloud and infrastructure entities, the retention TTL is 180 minutes (3 hours) and the purge TTL is 525,600 minutes (365 days). 

Kubernetes Entities

Application Performance Monitoring Entities

Third party names, logos, marks, and general references used in these materials are the property of their respective owners or their affiliates in the United States and/or other countries. Inclusion of such references are for informational purposes only and are not intended to promote or otherwise suggest a relationship between Splunk AppDynamics and the third party.