Getting Started with Ingest Keys

Overview

This guide introduces AppStatus Ingest Keys and covers:

• One key per signal: APM, errors, logs, RUM, serverless, cost, pipelines
• Separate keys per environment
• Shown once at creation — store it in your secret manager
• Rotate without downtime, revoke instantly
• Per-key rate limits and plan quota

What are Ingest Keys in AppStatus?

An ingest key authorises one workspace to send one kind of telemetry. Keys are deliberately narrow: a key that leaks from a browser bundle cannot be used to write logs, and no ingest key can read anything back out.

That scoping is what makes the RUM key safe to ship in your page source. It is public by design, and the only thing it can do is send browser telemetry to your workspace.

Key capabilities:

• Scope per signal so one leak does not become full access
• Separate keys per environment for safe revocation
• Rotation flow: create, deploy, then revoke the old key
• Immediate revocation — a revoked key stops accepting data at once
• Per-key rate limits with plan quota enforcement

What you will see

What the key list looks like

Scroll the table sideways to see every column.

Troubleshooting

Operational Guidance

• The RUM key ships in your page source and is public by design — that is why scopes exist.
• Revoke immediately on suspicion; a revoked key stops accepting data at once.
• If ingest suddenly stops, check the key rate limit and plan quota before debugging the SDK.

Step-by-Step Setup

Keys are quick to create and worth a minute of thought about scope. One key per signal per environment is the pattern that keeps a leak small and a revocation safe.

1. 1

   Create one key per signal

   Create a separate key for each signal you send — APM, errors, logs, RUM, serverless, cost, pipelines — and a separate set per environment.

   WhereIngest Keys → Create key

   Tip

   Reusing one key across signals turns a single leak into full ingest access. The scoping only helps if you use it.

2. 2

   Copy the value at creation

   The key value is shown once and never again. Copy it straight into your secret manager — not into a config file, a ticket, or a chat message.

   WhereIngest Keys → Create key → Copy
3. 3

   Reference it from configuration

   Point your application at the secret rather than embedding the value. The RUM key is the deliberate exception: it ships in your page source, because its scope lets it do nothing else.

   WhereYour application configuration
4. 4

   Set a rotation reminder

   Decide the rotation schedule before you ship, not after. Rotation is create new, deploy, then revoke old — done in that order, ingest never gaps.

   WhereIngest Keys → key detail

Configuration Options

Every option you can set, what each choice means, and what to pick. Use this as a reference while you fill in the form.

Feature Reference

Every feature, where to find it in the app, and what it does. Use this when you know what you want to do but not where it lives.

Next Steps

Continue building your monitoring stack: