reliant forge obs. It can be in any language, on any infrastructure: you add an OpenTelemetry SDK and a few environment variables.
The variables are the standard OpenTelemetry ones, so there is no Reliant SDK to install. The token decides which organization and environment the data lands in.
Before you begin
- A Reliant account in the organization the telemetry should belong to, with the
obs:writepermission to mint tokens. Owners and admins hold it. - The
reliantCLI v1.21.3 or later, which includes forge v1.6.1 (install). Your repository does not need aforge.yaml. - Your own terminal and browser. Ingest tokens are minted by a person, so this cannot be run by an agent or a CI job.
Sign in as yourself
Register the environment and mint a token
deploy/envs/prod.yaml (--write-config skips the question, --no-write writes nothing). Commit that file: every obs command reads the project from it.export line for each variable. The token is shown once and expires after 90 days at most.Set the variables where the app runs
obs init printed. Give each deployable its own OTEL_SERVICE_NAME. Set service.version to what you deploy, such as the git SHA or release tag: the issue list’s “first seen in” and obs check both key on it. Keep deployment.environment.name equal to the env name you passed to obs init.Add an OpenTelemetry SDK
OTEL_LOGS_EXPORTER=otlp) only if nothing already ships the app’s stdout, or every line arrives twice.Check that telemetry arrives
telemetry line shows when the newest log and span came in, and your service appears with its request rate, errors and p95. Then read the data itself:Rotate the token before it expires
list marks one in its last 14 days with “expires soon: rotate it”:rotate mints a replacement, and the old token keeps working for the grace period while you roll out the new header. obs tokens create prod --name <label> mints a separate token per cluster or CI system, and obs tokens revoke <token-id> --reason leaked cuts one off within minutes.What this does not do
- It does not build or deploy your app. The environment is registered as self-managed, and the platform never deploys there.
- There is no anonymous path. Reading telemetry needs a sign-in, and minting tokens needs a person with
obs:write. A CI job can read with a token that hasobs:read(credentials). - With no deploy recorded,
obs checkjudges a newservice.versionfrom the first time telemetry showed it, and marks the resultmarker INFERRED. A canary or slow rollout moves that moment. - A monitoring-only environment gets the built-in alerts (new and regressed issues, quota) and your organization’s alert receivers. Per-environment alert rules come from a Forge-deployed environment’s declaration (dashboards and alerts).
- The ingest token is a server-side secret. Never ship it in a browser bundle or a mobile app.
Troubleshooting
telemetry ingest tokens are minted, rotated and revoked by a person, not a machine credential
telemetry ingest tokens are minted, rotated and revoked by a person, not a machine credential
obs init ran with an agent’s or a pipeline’s credential. Run it yourself in your own terminal after reliant forge cloud login. The refused run may still have registered the env and written deploy/envs/prod.yaml; running it again reuses both and only mints the token.minting an ingest token needs a person who is a member of the organization holding the obs:write permission
minting an ingest token needs a person who is a member of the organization holding the obs:write permission
obs:write. Ask an owner or admin of the organization to grant it, or to run obs init for you.telemetry: nothing received in the last 24h0m0s
telemetry: nothing received in the last 24h0m0s
http/protobuf, and the header reads authorization=Bearer <token> with no extra quotes. Check that the token is not revoked (obs tokens list prod --all).env prod is declared in deploy/kcl/prod/main.k
env prod is declared in deploy/kcl/prod/main.k
reliant forge obs tokens create prod.