Beta
Traces and logs over OTLP/HTTP, protobuf or JSON. Metrics and gRPC aren't accepted.Set up
.env
OTEL_EXPORTER_OTLP_ENDPOINT=https://api.codeskop.com/v1/otlpOTEL_EXPORTER_OTLP_HEADERS=Authorization=Bearer cs_live_pk_…OTEL_EXPORTER_OTLP_PROTOCOL=http/protobufOTEL_SERVICE_NAME=checkoutotel-collector.yaml
exporters: otlphttp/codeskop: endpoint: https://api.codeskop.com/v1/otlp headers: Authorization: Bearer cs_live_pk_… service: pipelines: traces: receivers: [otlp] exporters: [otlphttp/codeskop] logs: receivers: [otlp] exporters: [otlphttp/codeskop]Use the project's public key. Set service.version and deployment.environment.name resource attributes to see releases and environments.
What becomes what
| Option | Type | Description |
|---|---|---|
| Server spans | HTTP or RPC | Incoming requests, by http.route (Network page, Requests your servers receive). |
| Client spans | HTTP | Outgoing API calls and failures (APIs your apps call). |
| exception span events | recordException | Issues, with stack traces and the request they happened in. |
| Error and fatal logs | severity ≥ ERROR | Issues. exception.* attributes give the class and stack trace; otherwise the log message. |
| Everything else | Internal spans and lower-severity logs are accepted and dropped. |
Request and API call monitoring follow the network monitoring and sampling on your plan, like the SDKs. Failed requests and errors are always kept. Exporter retries are de-duplicated. API Trust needs one of the Codeskop SDKs.