Use FaultLens to move from error capture to a connected diagnosis workflow that keeps issue context visible.
These docs are crawlable public guidance for current and beta FaultLens integration paths. Keep project API keys out of source control and avoid sending secrets in custom context.
You need a FaultLens workspace, a project API key, and the correct ingest host for your tenant or validation environment.
The SDKs are intended to capture application errors and diagnostics context without interrupting the host application flow.
Use this as a starting point and adjust environment, release, endpoint, and project identifiers for your workspace.
1. Capture the production error.
2. Attach environment and release context.
3. Review breadcrumbs and request context.
4. Add investigation notes and ownership.
5. Decide the next action while the context is still attached.These pages explain adjacent setup work that makes production diagnosis more useful after events start arriving.
FaultLens is a production issue diagnosis and error monitoring platform for SaaS engineering teams. It helps teams connect errors, releases, environments, and issue context so they can investigate production failures faster.
FaultLens is for SaaS engineering teams that need a focused way to diagnose production errors, connect them to releases and environments, and keep issue context in one investigation workflow.
Yes. FaultLens includes error monitoring, but its positioning is narrower than a full observability platform: it focuses on production issue diagnosis and the context needed to act on failures.
FaultLens documentation focuses on sending useful production error context into a diagnosis workflow rather than documenting a broad observability stack.
FaultLens has a public .NET SDK package named FaultLens.SDK and released JavaScript SDK packages for browser, Angular, and React integrations under the @faultlenshq npm scope. The current JavaScript packages are beta releases.