Faultline Documentation
Faultline is an observability platform for tracing, logs, metrics, and infrastructure monitoring — with built-in root-cause analysis that correlates a fault back to the deploy or commit that likely caused it.
This is where you'll find everything to get data into Faultline, use its core features, and administer your workspace.
Get started
- Quickstart — send your first traces, logs, and metrics to Faultline
- Send traces — instrument a service with OpenTelemetry
- Send logs — ship application and infrastructure logs
- Send metrics — collect host and service metrics
Explore core features
| Feature | What it does |
|---|---|
| Overview | Fleet-wide health dashboard with deploy markers |
| Traces | Distributed tracing across services, with span-level detail |
| Logs | Centralized log search, live tail, and correlation with traces |
| Metrics | Per-service metric charts with min/avg/max rollups |
| Services & Topology | Per-service health table and an interactive dependency graph |
| Dashboards | Pin metric panels into a shareable, named view |
| Incidents & Alerts | Rule-based alerting with an incident timeline and MTTR |
| Exceptions | Every errored/faulted span, with fault category and LLM verdicts |
| Deploy Correlation | Link faults to the deploy or commit that introduced them |
| Infrastructure Monitoring | VM and Kubernetes host/node/pod visibility |
| Messaging Queues | Span-derived producer/consumer throughput and latency |
| External APIs | Automatic visibility into outbound calls to third-party systems |
| Cost Meter | Track ingested data volume per signal over time |
Administer your workspace
- Authentication & SSO
- Team & Users
- Data Retention
- Integrations — Slack, WhatsApp, webhooks, GitHub
Run it yourself
Faultline can be self-hosted with Docker Compose or Kubernetes/Helm. See Self-Hosting.
Reference
- API Reference — the full REST API surface
- Support — FAQ and how to reach us