Product Guides
Settings
Use Settings to manage project identity, ingestion keys, access, members, roles, and billing.
Overview
Use Settings for project identity, ingestion keys, access, members, roles, and billing context. Settings is where setup values and team permissions are managed before telemetry can be trusted.
Use this page after you know the approximate symptom and need to decide which evidence should come next. Keep the service, environment, and time range consistent as you move from summary pages to request-level detail.
How to read this page
Use Project settings for identifiers and ingestion key management. Use Members, Access, and Roles to keep project permissions explicit. Use Billing when account ownership or plan state affects the workspace.
- Project identity
- Project values determine where telemetry lands and which workspace should show it.
- Ingestion keys
- Keys connect services to the project. Rotate them when ownership or exposure changes.
- Access
- Members and roles decide who can inspect, configure, and respond.
Investigation workflow
Use this sequence when you need to move from a broad symptom to evidence you can share with another teammate.
- 1
Before adding a new service, copy the project ingestion key and confirm environment naming.
- 2
After a team change, review members, roles, and key rotation needs.
- 3
If data lands in the wrong project, verify the key and project context first.
Interpretation note
Do not put ingestion keys in source code. Do not reuse vague service or environment values across unrelated deployments. Do not grant broad access when a narrower role is enough for incident response.
Related pages
Open Settings
Go to the live Settings page.
SDK Quickstart
Use Settings values during instrumentation.
Configuration
Review shared SDK environment variables.
Wrong service or environment
Fix telemetry that lands under the wrong labels.
Ingestion keys and access
Manage project keys and teammate permissions safely.
Service identity
Keep services, environments, versions, and deployments consistent.