Telemetry
Send every workflow run to your observability tool as an OpenTelemetry trace, send job logs alongside, or archive them to your own bucket.
Each workflow run can go to your observability tool as a trace: the run, its jobs and their steps, with where each job ran and how long it waited for a runner. Traces use the OpenTelemetry format and its CI/CD conventions, so Honeycomb, Grafana, Axiom or your own OpenTelemetry Collector can read them without setup.
Every job in your connected repos is included, whichever runner took it. You can also send job logs to the same tool, or keep them in your own bucket.
Set up
Section titled “Set up”- Open Settings → Telemetry. Owners and admins can change it.
- Under OpenTelemetry endpoint, pick where to send traces, or choose Other and paste any endpoint that accepts OTLP over HTTP with JSON. Traces go to the endpoint’s
/v1/traces. - Add the headers your tool wants, usually an API key. Values are stored encrypted and never shown again.
- Under What to send, set Traces to Every run. Save, then click Send test trace. A trace named
RUN RelayRunner testshows up in your tool.
From then on, each job goes out when it finishes and each run when it completes. Pointing telemetry at another endpoint or changing its headers shows in Activity.
| Span name | Description | When sent |
|---|---|---|
RUN {workflow} |
The run attempt, from when it started to when it completed. The root of the trace. | When the run completes |
{job name} |
One job, from when GitHub queued it to when it finished. | When the job finishes |
Waiting for a runner |
The time between GitHub queuing the job and a runner taking it. | With its job |
{step name} |
One step of the job. Skipped steps are left out. | With its job |
Failed runs, jobs and steps have an error status and an error.type.
Ids come from GitHub’s run and job ids, so a job sent early and its run sent later land in the same trace.
Attributes
Section titled “Attributes”The run span:
cicd.pipeline.name,cicd.pipeline.run.id,cicd.pipeline.run.url.full,cicd.pipeline.resultvcs.ref.head.name,vcs.ref.head.revision,vcs.change.id(the pull request number)relayrunner.run.attempt,relayrunner.run.event(push, pull_request and so on),relayrunner.run.title,relayrunner.run.actorrelayrunner.routed: whether the run went through the Routerrelayrunner.route.providerandrelayrunner.route.skipped: where the Router sent it, and what it passed over and whyrelayrunner.retry: whether this attempt was an automatic retry
Each job span:
cicd.pipeline.task.name,cicd.pipeline.task.run.id,cicd.pipeline.task.run.url.full,cicd.pipeline.task.run.result,cicd.worker.namerelayrunner.provider: where it ran, such asmachine,githubordepotrelayrunner.runner: the machine’s name or the runner typerelayrunner.labels: the job’sruns-onlabelsrelayrunner.queue.wait_msandrelayrunner.billed_minutesrelayrunner.cpu.p95,relayrunner.memory.p95_mb,relayrunner.cpus,relayrunner.memory_mb: on machines that report usage
The resource carries service.name (github-actions unless you change it), vcs.repository.name, vcs.repository.url.full and vcs.owner.name.
Job logs
Section titled “Job logs”Under What to send, set Job logs to Failed jobs or Every job to send logs too. They go to the same endpoint’s /v1/logs, with the same headers. Each job’s log goes out when the job finishes. Turning job logs on or off, or changing which jobs send them, shows in Activity.
- Each line is a log record with GitHub’s timestamp. Lines that start with
##[error]or##[warning]get that severity. - Each record carries the trace and span ids of its step, so a tool that shows traces can show a step’s lines with it.
relayrunner.step.numberandrelayrunner.step.namename the step. - The resource carries the repository and the job:
cicd.pipeline.name,cicd.pipeline.task.name,cicd.pipeline.task.run.id,cicd.pipeline.task.run.url.full,relayrunner.run.attemptandrelayrunner.job.conclusion. - A log over 20 MB keeps its first 16 MB and last 4 MB, with a line between that says how much was left out and links to the full log on GitHub.
Logs come from GitHub, which replaces your repository’s secrets with *** before it stores them. As a backstop, anything that looks like a credential, such as a GitHub or AWS key, a bearer token or a private key, is replaced with [redacted]. A value that was never stored as a secret can still show up, so treat logs in your tool with the same care as on GitHub.
Each log costs one call from your GitHub App installation’s hourly API limit, which routing also uses. When fewer than a quarter of those calls are left, logs wait until the limit resets. Failed jobs are the default for this reason.
Log archive
Section titled “Log archive”Under Log archive, job logs go to a bucket you own: Amazon S3, Cloudflare R2, Google Cloud Storage, or any other service that speaks the S3 API. This works with or without a telemetry endpoint.
- Pick the service, then enter its endpoint, the bucket’s name and its region (
autofor R2 and Google Cloud Storage). - Optionally, enter a folder to put the logs under, like
github/. - Enter an access key that can write objects to the bucket. For Google Cloud Storage, use an HMAC key. The key is stored encrypted and never shown again.
- Set Job logs to Failed jobs or Every job, save, then click Write test file. A file named
relayrunner-test.ndjson.gzshows up in the folder.
Each job’s log becomes one gzipped NDJSON file at {folder}{owner}/{repo}/{yyyy}/{mm}/{dd}/{run id}-{attempt}/{job id}.ndjson.gz, dated by when the job finished. A job always lands at the same path, so a retry replaces the file instead of adding another.
The first line describes the job:
{ "type": "job", "repository": "acme/app", "workflow": "CI", "job": "test", "job_id": 123, "run_id": 456, "run_attempt": 1, "conclusion": "failure", "url": "https://github.com/acme/app/actions/runs/456/job/123"}Each line after it is one log line:
{ "type": "line", "time": "2026-11-19T21:04:05.123456700Z", "level": "error", "step": 4, "step_name": "Run tests", "message": "Error: 2 tests failed"}The same size cap, redaction and API limit apply as for job logs. Turning the archive on or off, moving it to another bucket or folder and changing its access key show in Activity.
When sending fails
Section titled “When sending fails”If your endpoint or bucket is down or rate limiting, sending retries for about an hour. If it refuses the key, the error shows in Settings → Telemetry. After three days of nothing but errors, sending pauses until you save the settings again. A day with nothing to send starts the count over, so a bucket that only gets the occasional failed job doesn’t pause over errors days apart. When a job’s log can’t be sent, for example because GitHub no longer has it, the reason shows there too.
What gets sent
Section titled “What gets sent”Traces hold repository and workflow names, branches, commit SHAs, pull request titles, GitHub usernames, job and step names, timings and where each job ran. They never hold logs, secrets or environment variables.
With job logs on, the log lines go out as well. Nothing keeps a copy on the way: each log streams from GitHub to your endpoint or bucket.