Docs
Issues
Issues are where Foam collects the problems it finds in your system. Instead of a stream of raw alerts, each issue is a detected, grouped, and root-caused problem with the evidence attached — so your team starts from the answer, not the symptom.
Foam finds problems for you
Foam watches your telemetry continuously — errors, failed requests, latency drift, broken user flows, and misbehaving agents. When something breaks, it becomes an issue automatically. You don’t need to define every failure mode up front; Foam also catches the problems nobody thought to alert on, like an export that silently fails for every large account.
Root cause, not just symptoms
Every issue comes with an investigation already done. Foam correlates the failure with deploys, config changes, logs, and traces across services to explain what actually happened — for example, that a config deploy halved a connection pool and requests started queueing. The evidence trail is attached, so verifying the conclusion takes minutes, not an afternoon.
Impact you can see
Issues quantify who and what is affected: how many users or accounts hit the problem, how often, and since when. That makes prioritization straightforward and gives support a proactive list of affected customers instead of a queue of mystery tickets.
Routed to the right person
When an issue needs a human, Foam pings the responsible engineer with the report — the root cause, the impact, and the evidence — so they start with everything in hand. From there you can dig deeper in chat, and when a fix is code-shaped, ask Foam to propose the pull request.