Error Root Causing
When an exception occurs, Foam traces it to a root cause and notifies the relevant person. Foam refers to exceptions as issues — runtime errors captured from your services.
Continuously ingests errors
Foam listens to errors from all instrumented services. Nothing is sampled; every error is looked at.
Detects errors worth investigating
Foam assesses which errors are worth investigating by detecting spikes and first-time appearances. Known, stable errors are not flagged. This helps us keep your system noise free.
Runs root cause analysis
Foam investigates the error using related logs, traces, and metrics across services to produce a root cause analysis.
Identifies the responsible person
Foam uses the root cause result — not git blame — to determine who should be notified. This means the right person is identified based on what actually caused the issue, not just who last touched the file.
Sends a Slack notification with the RCA
The responsible person (and/or a channel) gets a Slack message linking to the RCA summary.