Introduction

Errorgap helps product and engineering teams understand production failures without switching between disconnected tools. It brings errors, stack traces, request context, logs, deploy history, uptime checks, and incident activity into one project workspace.

What is Errorgap?

Errorgap starts with error monitoring. When your application reports an exception, Errorgap groups related occurrences, keeps the relevant backtrace and runtime context, and gives your team a shared place to triage the issue.

From there, Errorgap connects the surrounding operational signals: recent logs, deploys, uptime failures, performance changes, and infrastructure activity. The goal is to make the next action clear, whether that is assigning an owner, opening an issue, muting noise, or shipping a fix.

How Errorgap is organized

Most work happens inside a project. A project usually maps to one application, service, or deployable unit. Each project has its own error stream, settings, integrations, and access rules.

• Projects collect events from one app or service.
• Environments separate production, staging, review apps, and other runtime targets.
• Error groups combine repeated occurrences that share the same underlying failure.
• Incidents track active operational work around a failure or outage.
• Integrations connect Errorgap to places your team already works, such as Slack, GitHub, GitLab, Jira, and webhooks.

First-run workflow

The fastest way to see value is to create a project, install an SDK, and send one deliberate test error from a non-production environment.

1. Create a project for the application you want to monitor.
2. Install the SDK for your runtime.
3. Configure the SDK with the project key shown in project settings.
4. Trigger a test exception and confirm it appears in the project error list.
5. Open the error group and review the message, backtrace, context, and timeline.

// Example shape only. Use the SDK guide for your runtime.
Errorgap.init({
  projectKey: "egp_your_project_key",
  environment: "staging",
  release: "2026.06.10"
});

Where to go next

Continue with project creation, SDK installation, and a safe test error. After ingestion works, review project settings, redaction, and agent access before expanding monitoring to logs, infrastructure, performance, or replay evidence.