Identify the telemetry in scope
Specify the service data covered by the review and establish who owns the retention decision.
Sense / AI operations
Plan telemetry retention around investigation needs.
Sense helps teams plan how telemetry is stored and retained within Unified Observability. Review the investigation needs of a service and translate them into an explicit retention policy that the responsible owners can assess over time.
Retention policiesSense
Prepare a retention policy review for invoice API logs and traces used in billing investigations.
In the workspace
Telemetry scope
Invoice API · Logs and traces
Investigation need
Billing review and incident follow-up
Policy checkpoint
Retention period · Owner review
Make the retention decision explicit for each telemetry scope.
How it works in Sense
The service owner has a defined telemetry scope and a retention decision to review with the teams that depend on it. The policy can be assessed against investigation requirements and applicable data-handling rules before it is applied.
Understand the investigation window
Discuss how incident follow-up and billing reviews use historical evidence, including which records they need to remain available.
Review the policy over time
Confirm the proposed retention period and revisit it when investigation practices or data-handling requirements change.
Bring Sense to your team.
Explore retention policies around your company’s workflows.