cleanmatic:telemetry

Telemetry for product owners works by deterministically gathering data from local telemetry sinks and rendering diagnostic views across eight lenses. It provides a non-editing narrative over usage, health, and reliability to surface actionable signals.

Yes, you can render observability data as ascii, markdown, mermaid, or json formats. The diagnostic process is strictly read-only, ensuring it surfaces operational health and data quality signals without impacting the underlying source data.

Yes, the telemetry reader supports generating plain-language diagnostic reports in both Vietnamese and English. This allows product owners and engineers to review operational health and workflow reliability in their preferred language.

The best way to check internal-quality checks is by applying the validate and reliability diagnostic lenses. This approach deterministically surfaces whether internal checks pass and if workflows are healthy, providing an honest view of operational status.

Yes, you need PyYAML installed as a dependency to run local diagnostics and observability checks. This library supports the underlying processing logic required to parse configurations and render the telemetry outputs.

Your telemetry report shows artifact_heat and forensics data because these are two of the eight diagnostic lenses used to evaluate product health. They highlight data quality and operational signals deterministically gathered from local sinks.