Concepts & Reference
Ingestion Keys And Access
Understand how project ingestion keys and teammate access fit into safe Vight setup.
Concept
Understand how project ingestion keys and teammate access fit into safe Vight setup.
An ingestion key lets an instrumented service send telemetry to a Vight project.
Project access controls who can view, configure, or respond inside the workspace.
Keys and access should be reviewed when services, teams, or deployment ownership changes.
Examples
- Deployment secret
- Store the ingestion key in the deployment environment or secret manager used by the service.
- Key rotation
- Rotate a key after ownership changes, accidental exposure, or service retirement.
- Access review
- Review project members and roles when incident responders, developers, or operators change.
How Vight uses it
Copy ingestion keys from Settings into deployment secrets, not application source code. Rotate keys when a service is retired, access changes, or a key may have been exposed. Use roles and member access to keep response actions limited to the right teammates. Review Settings before adding a new service, environment, or team to the project. If data appears in the wrong project, verify the key and project context first.
Usage guidance
Do not commit ingestion keys to source code. Use separate projects or environments when teams need clean operational boundaries. Rotate first, then redeploy services with the replacement key. Keep access broad enough for incident response and narrow enough for safe administration.