Docs
Get started with Foam
Foam analyzes each one of your services and builds a custom OpenTelemetry package tailored to the exact stack and set up, proposing its installation PRs within hours. It works alongside any other observability tool so you can try it out without changing anything about your set up.
How it works
A single identifier connects logs, traces, and spans end to end, so every trace resolves to what it relates to: the exact frontend click that started it, the slow database query behind a crashing checkout page, or the agent run that burned tokens retrying a failing call. Your telemetry is accessible and connected across your entire stack.
Signals Foam ingests
- Distributed traces, logs, metrics, and errors across your services
- Session replays, Web Vitals, and network activity in the browser
- LLM and agent workloads: prompts, responses, token usage, and multi-step runs
- Background jobs: workers, queues, and scheduled tasks
Traces
The path a request takes through your system, service by service. When checkout fails because a downstream config change flooded a connection pool three services away, traces are how Foam follows that chain.
Logs
What your code is actually saying at runtime. Error messages, warnings, state changes. Foam uses logs to understand what happened inside a service at the moment something went wrong.
Metrics
Numbers over time: request rates, error rates, latency, memory usage. Foam uses metrics to spot when something deviates from normal.