Runtime telemetry

Send what is actually running

Point an OpenTelemetry exporter here and the architecture map gains a second half: which files traffic went through, how slow they were, and which calls your running system made that the scan did not find.

What leaves your process

OpenTelemetry’s own SDK does the instrumentation — there is no agent of ours inside your application. Of what it sends, we keep counts and latency buckets against a file or an edge, and nothing else. No request bodies, no user identifiers, no URLs, no trace ids, and no raw spans. A trace id is a handle onto one customer’s request; following one is a separate thing we have not built.

Step 1: A project key
Telemetry belongs to an organisation, and a key is how a running system says which one it is — the same key that publishes a scan.
Sign in
2
Step 2: Point an exporter at it
Two of these are the ones everybody’s first attempt misses. The protocol, because OpenTelemetry defaults to protobuf and this endpoint reads JSON; and the endpoint, which is a base — the SDK appends /v1/traces itself, so pasting the full path produces a 404 that looks like we are down.
environment
```
OTEL_EXPORTER_OTLP_ENDPOINT=https://dev.mlreps.com/api/observe
OTEL_EXPORTER_OTLP_PROTOCOL=http/json
OTEL_EXPORTER_OTLP_HEADERS=Authorization=Bearer <your ingest key>
OTEL_SERVICE_NAME=your-service
# and the deployed commit, so traffic is drawn on the scan it belongs to
OTEL_RESOURCE_ATTRIBUTES=service.version=$GIT_COMMIT
```
3
Step 3: Or check the path by hand
An empty batch is accepted and tells you whether the key works. The response to every batch is the diagnostic: how many calls arrived, how many were placed on the graph, and a named count for each one that was not.
in a terminal
```
curl -X POST https://dev.mlreps.com/api/observe/v1/traces \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <your ingest key>" \
  -d '{"resourceSpans":[]}'
```
Step 4: Then look at it
Traffic appears under the map on the architecture screen. If spans arrive and none of them can be placed, that screen says so rather than showing a quiet system — the two are different failures and only one of them is yours.
Open the architecture map
Spans are placed by code.filepath and code.function, which most SDKs do not send by default. Without them a span carries a route at best, and everything lands on the handler rather than the code inside it. The endpoint is /api/observe/v1/traces.

What leaves your process

Point an exporter at it

Two of these are the ones everybody’s first attempt misses. The protocol, because OpenTelemetry defaults to protobuf and this endpoint reads JSON; and the endpoint, which is a base — the SDK appends /v1/traces itself, so pasting the full path produces a 404 that looks like we are down.

environment

OTEL_EXPORTER_OTLP_ENDPOINT=https://dev.mlreps.com/api/observe
OTEL_EXPORTER_OTLP_PROTOCOL=http/json
OTEL_EXPORTER_OTLP_HEADERS=Authorization=Bearer <your ingest key>
OTEL_SERVICE_NAME=your-service
# and the deployed commit, so traffic is drawn on the scan it belongs to
OTEL_RESOURCE_ATTRIBUTES=service.version=$GIT_COMMIT

Or check the path by hand

An empty batch is accepted and tells you whether the key works. The response to every batch is the diagnostic: how many calls arrived, how many were placed on the graph, and a named count for each one that was not.

in a terminal

curl -X POST https://dev.mlreps.com/api/observe/v1/traces \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer <your ingest key>" \
  -d '{"resourceSpans":[]}'

Then look at it

Traffic appears under the map on the architecture screen. If spans arrive and none of them can be placed, that screen says so rather than showing a quiet system — the two are different failures and only one of them is yours.

Open the architecture map

Spans are placed by code.filepath and code.function, which most SDKs do not send by default. Without them a span carries a route at best, and everything lands on the handler rather than the code inside it. The endpoint is /api/observe/v1/traces.

What leaves your process

Step 1: A project key

Step 2: Point an exporter at it

Step 3: Or check the path by hand

Step 4: Then look at it

What leaves your process

Step 1: A project key

Step 2: Point an exporter at it

Step 3: Or check the path by hand

Step 4: Then look at it