Diagnosis workspace

Turn evidence into a defensible next action

Your tools and credentials stay local. A client you control runs the checks; Tellagen records the focus question, working hypothesis, source audit, evidence gaps, and responder-approved next actions with the incident.

Tellagen diagnosis workspace showing the focus question, working hypothesis, confidence, open question, audited sources, evidence groups, one coverage gap, and a recommended response action.

Static product preview

Review the fictional checks, evidence links, open gap, confidence rationale, and responder decision.

Open the diagnosis workspace (opens in a new tab)

Frame

Start with the question, scope, and uncertainty

The Diagnosis path keeps the focus question, affected services, time window, playbook, confidence, and open questions visible. Follow-up required remains explicit when the available evidence cannot support a conclusion.

Inspect

See what supports the likely cause—and what doesn't

The source audit records which sources ran, failed, or were unavailable. Findings keep attached evidence references, while lineage status marks those links matched, partial, or unmatched—so responders can review gaps before accepting a cause or next action.

Tellagen evidence lineage comparing finding evidence references with recorded Grafana and GitHub diagnosis checks and showing a partial match with one unmatched reference.

Act

Promote only what responders have reviewed

Accepted findings can become timeline events with their evidence links. Recommended follow-ups can become assigned incident actions, keeping diagnosis, mitigation, and the final review connected without automatic incident changes.

What a diagnosis leaves behind

The outcome is not just a paragraph. Tellagen retains the investigation boundary, provenance, uncertainty, and reviewed response handoff.

Scope and playbook

Affected services, time window, selected runbook version, and source readiness define the investigation boundary.

Evidence provenance

Trace steps, source audit, checked evidence, gaps, and lineage show how the conclusion was formed.

Explicit uncertainty

Confidence, open questions, and follow-up required states stay visible beside the working hypothesis.

Response handoff

Reviewed findings move to the timeline and accepted recommendations become owned incident actions.

Frequently asked questions

Does Tellagen run a cloud agent inside my infrastructure?

No. An MCP-capable client that you control picks up the diagnosis and uses its locally configured tools. Tellagen stores the run context and reviewable results, not your infrastructure credentials.

Which tools can a diagnosis use?

The client can use the tools available in its environment, such as Grafana, Kubernetes, GitHub, documentation, logs, and CLI integrations. Tellagen provides sanitized source metadata and records availability gaps when required access is missing.

Does a finding automatically change the incident?

No. Findings and recommended actions remain reviewable. A responder decides whether to promote a finding into the timeline or accept a recommended action.

Ready for the record

Start a diagnosis your team can defend

Keep the question, checked sources, missing evidence, conclusion, and approved next action reviewable together.