Standard OpenTelemetry
Send traces, metrics and logs over OTLP/HTTP. Protobuf is the default, and JSON and gzip are accepted. OTLP/gRPC is available over TLS on port 4317.
Platform
Point OpenTelemetry at your workspace and watch the first data arrive.
Connect data is a guided setup in the sidebar. Choose your language, create an ingest token, paste the settings into your service, and the page tells you when the first data arrives.
What you get
A guide for your language
Node.js, Python, Java, .NET, Go and Ruby each have a short guide, and so does the OpenTelemetry Collector.
Bring the metrics you already collect
The docs have Collector recipes for Prometheus, StatsD, Telegraf and SNMP.
How it works
Open Connect data
Choose your platform from the list.
Create an ingest token
Admins create one in the wizard. The secret is shown once, so copy it then.
Paste the settings
Put the endpoint and token into your service's OpenTelemetry settings, shown below.
Watch it arrive
The page checks for data and shows Data received when the first event lands. A curl command sends a test event if you want to try it by hand.
OTEL_EXPORTER_OTLP_ENDPOINT=<the endpoint Connect data shows you>
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
OTEL_EXPORTER_OTLP_HEADERS=Authorization=Bearer%20<your ingest token>
OTEL_SERVICE_NAME=payment-apiThe service name is what appears on the Services page.
Other ways in
- Log shippers. Fluent Bit and Vector can send logs over OTLP. The HTTP JSON shippers carry logs only, up to 1 MB and 500 events per request.
- Connectors. Data sources lists connectors for AWS, Azure and Google Cloud.
- Host agent. A download for Linux or Windows that reports CPU, memory and load every 30 seconds.
Send the first span.
A trial workspace is enough to try every step above.