General settings

Project settings control how one application identifies itself, accepts events, exposes evidence, and protects sensitive data. Review settings before production rollout and after major ownership or traffic changes.

Project identity

The project name, slug, ID, language, and framework help teammates identify the monitored application. Keep the name human-readable and stable; use environments and releases for runtime distinctions.

Project API key

SDKs and event sources use the project API key to send data into the project. Treat it as a secret. Store it in environment variables or secret managers, not in source code.

• Copy the key when installing an SDK or configuring errorgap-agent.
• Rotate the key if it is exposed in a repository, log, chat, or support ticket.
• Update all SDKs and agents that send to the project immediately after rotation.

Event throttling

Event throttling helps control noisy projects and unexpected spikes.

• Sample rate accepts a fraction of repeated events. Use values below 1.0 for high-volume noise.
• Rate limit per minute caps burst intake. Set it to 0 only when burst limiting should be disabled.
• Error quota cap limits accepted occurrences. Set it to 0 for no explicit cap.

Lowering intake can reduce noise, but it can also hide rare context. Prefer fixing the source of noisy events before permanently sampling important production failures.

Privacy controls

Project privacy settings include redaction rules and MCP exposure toggles. Use them to make a sensitive project stricter than the organization default.

• Add project-level redaction for service-specific secrets.
• Disable agent access to categories the project should not expose.
• Keep request parameters restricted unless automated investigation truly needs them.

Session replay

Session replay settings decide whether the project can collect replay evidence and how that evidence is made available during error and incident investigation. Review replay settings alongside redaction rules because replay data can include user interaction context.

When to change settings

• Rename a project when the owning service or product name changes.
• Rotate the API key after exposure or when handing off ownership.
• Adjust throttling when event volume changes materially.
• Review privacy settings before enabling new integrations, agents, or replay capture.