Issues are the main entry point for telemetry control in Tero.An issue is a finding that needs review: cost waste, compliance exposure, signal-quality risk, or a check result you can turn into a policy action. Tero shows the issue with evidence, provenance, status, severity, affected service, and a recommended next step.
The Issues workspace combines filters, a work queue, and issue detail. Open in demo
Tero starts with issues so each policy traces back to a specific problem you reviewed. You need to know what Tero found and what evidence supports acting on it.A typical review goes like this:
Open an issue.
Review the evidence and provenance.
Inspect the recommended policy or action.
Deploy, ignore, or continue investigation.
Track policy state, runtime state, and impact.
Cost and Compliance lanes group issues by outcome. Checks show the detector inventory behind many issues. Services and Log events show the catalog context that helps you judge whether the recommendation is right.
Issue rows show status, severity, age, title, affected service or team, check type, and domain. The current domains in Tero are Cost and Compliance.Issue detail shows the review context:
A summary of what Tero found
A policy card when Tero recommends a policy
Related log events or affected fields
Evidence and timeline entries
Actions such as Ignore or Deploy policy
Tero can also show an active policy link when a policy already addresses the issue.
Use the Issues workspace to filter by severity, service, team, domain, check, linked issue, and status. The queue supports issue search, status selection, and loading more results.Use All when you want the complete queue. Use Cost or Compliance when you are reviewing a specific lane.
