From f2b91718a8a081c06e17ca9bc3ceb18c2be63a2e Mon Sep 17 00:00:00 2001 From: Simon van Lierde Date: Wed, 14 Oct 2026 00:03:39 +0200 Subject: [PATCH] docs: use r9lab-api as the example service name --- docs/ONBOARDING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ONBOARDING.md b/docs/ONBOARDING.md index eebdc7d..2347e36 100644 --- a/docs/ONBOARDING.md +++ b/docs/ONBOARDING.md @@ -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