Settings

Settings is where your workspace’s own configuration lives — the OTLP credential, the notification webhooks, appearance, your account, and (when enabled) your plan. Most of it is self-explanatory; this page is the map of what is where.

It lives under Admin & Governance → Settings. Sections that depend on a workspace feature — Alerting and Billing — appear only when that feature is on.

Connecting your app

Settings → App Onboarding holds your Project API Key and the ready-to-paste exporter config, the same credential the getting-started flow shows you. You can show / hide the key, copy it, and see when it was created and last used. The Example Configuration card offers Environment Variables, OTel Collector, Node.js and Python snippets, each built with your real endpoint and key.

A Connection Check (“Check for traces”) on the same screen polls for arriving telemetry and tells you what it sees; when nothing arrives it links straight to the connection diagnostics guide.

Caution

Regenerate API Key (in the section’s Danger Zone) invalidates the current key immediately — any service still using the old key stops sending until you update it.

Alerting webhooks

Settings → Alerting is where the notification side of Incidents is configured, on the Webhooks tab. Add Webhook takes a Name, a URL, an optional signing secret (sent as an X-Atrim-Signature HMAC-SHA256 header so you can verify deliveries), and a severity filter — Critical / Warning / Info — so a webhook only receives what you choose. Each webhook can be paused, edited, deleted, and test-fired in place, so you can confirm it works before an incident depends on it.

Tip

Paste a Discord webhook URL into the same URL field and nothing else changes — atrim.ai recognises the Discord host and formats the payload as a Discord embed automatically. Every other URL receives the standard atrim.ai JSON envelope.

Email needs no setup here: incident notifications also go to your sign-up address by default. A Detection tab shows that detection runs automatically every five minutes and lets an admin convert pending findings to incidents on demand.

Appearance

Settings → Appearance sets the colour scheme — System, Light, Dark, or the branded atrim.ai mode — saved to your account. A Service Topology control here, Show external dependencies, toggles whether uninstrumented peers (databases, caches, queues, third-party APIs) inferred from outbound calls are drawn on the map. Turn it off to see only services that report telemetry of their own.

General and account

• Settings → General shows your Tenant ID and a live Platform Status readout. Its Danger Zone holds Reset Tenant Data — a one-action wipe of all telemetry and analysis (traces, logs, metrics, topology, baselines, incidents) that keeps your settings, API keys, webhooks and billing. It is handy right after onboarding with a test app. Only a workspace owner or admin can run it; a member sees why it is unavailable rather than a dead button.
• Settings → Profile shows your email and connected sign-in providers, and can delete your account.
• Settings → Billing (when enabled) shows your plan or trial and opens the Stripe portal to manage your card, invoices or cancellation — those details deliberately live in Stripe, not here.

Note

Some operator-only tools that manage the deployment itself aren’t part of your workspace and won’t appear for your account.

Connect your appThe endpoint, the auth header, per-language setup, and troubleshooting when nothing arrives.

IncidentsWhat those webhooks deliver — the detect → notify → resolve loop they plug into.