Error monitoring for SaaS engineering teams

What error monitoring means in FaultLens

FaultLens captures application errors and diagnostic context from supported SDKs so engineering teams can see production failures with enough detail to start investigation.

The monitoring surface is application-focused: exceptions, messages, stack traces where available, SDK context, release labels, environments, and event details.

• Capture backend exceptions from .NET services using FaultLens.SDK.
• Capture frontend errors from browser, Angular, and React applications using released beta JavaScript SDK packages.
• Use release and environment values to filter production, staging, and deployment-related error signals.

Backend and frontend SDK setup

FaultLens documents SDK setup for .NET, browser JavaScript, Angular, and React applications. Sample repositories are available for teams that want to run a working integration before wiring their own application.

SDKs are designed to send events without interrupting the host application flow, and frontend SDKs can attach browser diagnostics context such as route, referrer, user agent, user ID, and tags.

Stack traces, events, and alerts

Error monitoring starts with the raw signal: what failed, when it happened, which runtime emitted it, and which release or environment was involved.

FaultLens is intended to turn those monitored events into developer-visible production failures that can be routed, reviewed, and connected to issue context.

• Use stack traces and exception metadata where the SDK can provide them.
• Use environment and release values to understand whether a failure is isolated or tied to a deployment.
• Use notifications and team workflows to make important production failures visible to developers.

Where to go next

If your team is choosing an error monitoring tool, start with SDK setup and sample applications. If your team already receives error events but struggles to resolve them quickly, review the production issue diagnosis workflow.