Skip to content

docs: use r9lab-api as the example service name #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
simonvanlierde merged 1 commit into from
Oct 13, 2026
Merged

docs: use r9lab-api as the example service name #53

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/ONBOARDING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ Never expose 4317/4318 directly.
## The conventions

- **`service.name`** is required: one stable name per deployable unit
(`relab-api`, not `relab-api-prod-2`). Dashboards key on it.
(`r9lab-api`, not `r9lab-api-prod-2`). Dashboards key on it.
- **`project`** and **`env`** are both required resource attributes: `project`
is the name `bootstrap.sh` was run with, `env` is `prod`, `staging`, or
`dev`. Together they are what every alert and dashboard filters on, and a
Expand Down
Loading