Skip to main content
Insights answers the question you have right after agents start failing: what is failing, why, and what to do about it. The Komodor Agentic Operation Platform (KAOP) groups related failures into ranked issues, shows the reason each one reported verbatim, and attaches a recommendation produced by a real agent investigating your account. Find it under Improve → Insights.

​
What the page tells you

The header figures cover the last 30 days of account activity: Below that, a 30-day activity heatmap plots run volume and failures day by day, so a bad day is a visible block rather than an averaged-away dip. Five charts break the same window down further:
  • Run trend — recent volume.
  • Run status — the current outcome distribution across Queued, Claimed, Running, Succeeded, Failed, and Cancelled.
  • Agent activity — runs by agent, each row split into succeeded, failed, and active.
  • Model breakdown — the run mix by model.
  • Failure causes — failures by category, using the categories below.
Insights is fixed to a 30-day window. If you need a shorter or longer period for reliability, the Fleet health Analytics tab offers Today, 7 days, and 30 days.

​
How failures are categorized

This is the part worth understanding, because it is what makes the rest trustworthy. KAOP segments a failing or stuck run only from structural signals it can prove — the run’s status, the shape of its span tree, and the agent’s presence. It never guesses a cause by matching substrings in an error message.
Why prose matching is refused. An error string is written by whatever failed, in whatever wording it chose, and it changes without warning. A classifier built on it produces confident labels that are sometimes wrong, and a wrong label is worse than no label — you go and check the thing it named instead of the thing that broke. So a run KAOP cannot prove stays Unclassified failure, with its real error text attached, rather than being forced into a plausible bucket.

​
The reason is shown verbatim

Instead of re-labelling what a run reported, KAOP shows the failure reason exactly as it arrived — Missing Datadog credentials. Set DD_API_KEY and DD_APP_KEY… reads as that sentence, not as “configuration error”. The category tells you where to look; the verbatim reason tells you what happened. Grouping uses the category together with the normalized reason, so identical failures collapse into one issue instead of a hundred rows.

​
Needs attention

The Needs attention panel is the ranked list of issues — “ranked failure clusters with an agent-backed recommended fix”. Each card carries:
  • The category badge and a confidence badge (High, Medium, or Low confidence).
  • A Growing marker when the issue is getting worse rather than sitting still.
  • The issue title and why it happened.
  • The scale: how many runs, how many agents, and when it was last seen.
  • The recommendation, once produced.
Ranking is by severity first, then by how many runs an issue affects. Severity is derived, not assigned: an issue is high severity when it is growing or affects at least five runs, medium when it was last seen inside the window, and low otherwise. High-severity issues are treated as incidents. An issue carries a lifecycle you can read on it — open, investigating, or resolved — which moves as an investigation starts and finishes.

​
Recommendations come from a real agent run

A recommendation is not a lookup in a table of canned advice. When you ask for one, KAOP starts a run on a chat-capable agent, which investigates the issue using your account’s own tools and returns two things: a one- or two-sentence tagline for the card, and a full root-cause write-up behind Details.
1

Pick who recommends

The Recommendations by control selects which chat-capable agent investigates. Your choice is remembered, so the agent that knows your environment best stays selected.
2

Ask for a recommendation

Press Recommend. The card shows Investigating… while the agent works.
3

Read the tagline, then the detail

The tagline is the answer in one line. Details expands the full root-cause analysis, with the evidence the agent used.
4

Continue interactively

Chat — or Continue in chat from inside the details — takes you into the same session, prefilled with the failure context. You are continuing the investigation, not restarting it.
Because a recommendation is a run, it has an evidence trail like any other run. If a recommendation looks wrong, you can read exactly which tools the investigating agent called and what they returned — which is the difference between an opinion and a traceable conclusion.

​
Acting on each category

The category tells you where the fix lives, and each issue links to the right place.
KAOP recommends and never remediates on its own here. There are no automatic retries, restarts, credential rotations, or scale-ups behind an issue. Every fix is yours to make, which is why the recommendation names the place to make it.

​
Where else issues appear

The account Overview carries a compact form of the same panel — the top reliability issues from the last 30 days, with a View insights link. It is deliberately read-only: it never starts a recommendation run, so opening your home page costs nothing.

​
Next steps

Fleet health

Live presence, capacity, and the per-agent reliability ranking.

Runs & evidence

The span tree the categories are proved from.

Troubleshooting

The fixes for each of these categories, step by step.

Evaluations

A run that succeeded can still be wrong. This is how you find out.