Hosted OpenTelemetry
One OTLP endpoint per Logs stack for logs, traces and metrics. Standard OpenTelemetry, included on every plan.
Trusted by engineering teams worldwide
Hosted OpenTelemetry gives every Logs stack a managed OTLP/HTTP endpoint at https://{stackId}-otel.logit.io (HTTPS on port 443, http/protobuf). Logit.io runs the OpenTelemetry Collector for you, so your apps can send straight from an OpenTelemetry SDK or zero-code agent without running a Collector yourself. If you already run a Collector, point its OTLP/HTTP exporter at the same endpoint (Basic auth). There's no Logit agent to install.
It's included on every plan, not an add-on. New Logs stacks have it switched on automatically. Existing Logs stacks are opt-in: an account owner or administrator, or a stack administrator, selects Switch on in the Hosted OpenTelemetry card on the stack's Endpoints page. Setup takes a few minutes.
Start a free trial · OpenTelemetry Collector docs · OpenTelemetry on Logit.io
One endpoint, three signals
Logs, traces and metrics all go to the same URL, so you configure your exporters once.
- Logs are stored in your Logs stack.
- Traces go to the APM stack.
- Metrics go to the Metrics stack.
If you send traces without an APM stack, or metrics without a Metrics stack, the request is accepted and that data is dropped. Add the stack before you rely on that signal.
Collector and SDK configuration
Logit.io runs the OpenTelemetry Collector for you, so your apps can send straight from an OpenTelemetry SDK or zero-code agent without running a Collector yourself.
If you already run a Collector, use OpenTelemetry Collector Contrib (otelcol-contrib) and point its otlphttp exporter at the same endpoint with Basic auth. The Basic auth extension ships in the Contrib distribution, so use otelcol-contrib for this config to work as pasted. The username is {stackId}-otel and the password is the stack's Hosted OpenTelemetry API key:
receivers:
otlp:
protocols:
http:
endpoint: 0.0.0.0:4318
extensions:
basicauth/logit:
client_auth:
username: {stackId}-otel
password: ${env:LOGIT_OTEL_API_KEY}
exporters:
otlphttp/logit:
endpoint: https://{stackId}-otel.logit.io
auth:
authenticator: basicauth/logit
service:
extensions: [basicauth/logit]
pipelines:
logs:
receivers: [otlp]
exporters: [otlphttp/logit]
traces:
receivers: [otlp]
exporters: [otlphttp/logit]
metrics:
receivers: [otlp]
exporters: [otlphttp/logit]OpenTelemetry SDKs can export straight to the endpoint with the standard environment variables. The quickest route is the dashboard: copy its ready-made Header value and use it as the whole OTEL_EXPORTER_OTLP_HEADERS value. To build it yourself, set LOGIT_OTEL_BASIC_AUTH to the Base64 encoding of {stackId}-otel:{apiKey} (your username, a colon, then the stack's Hosted OpenTelemetry API key). Your shell expands the variable below:
OTEL_EXPORTER_OTLP_ENDPOINT=https://{stackId}-otel.logit.io
OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf
OTEL_EXPORTER_OTLP_HEADERS=Authorization=Basic%20${LOGIT_OTEL_BASIC_AUTH}Hosted OpenTelemetry takes OTLP over HTTP only, on port 443. gRPC isn't supported, so set SDKs to http/protobuf. See the OpenTelemetry Collector integration docs for more.
Set up from the dashboard
Onboarding shows your stack's endpoint, username, API key and Header, each with a Copy button. Its copy-paste setup comes prefilled with your stack's own details, so a pasted config works without editing.
The endpoint shows as setting up until it's ready. Setup takes a few minutes, and then the connection details appear.
Existing stacks: switch it on
Logs stacks created before Hosted OpenTelemetry are opt-in: an account owner or administrator, or a stack administrator, selects Switch on in the Hosted OpenTelemetry card on the stack's Endpoints page. Setup takes a few minutes. Data you sent before switching on isn't backfilled.
You can rotate the API key from the same page.
Monitored endpoints
Hosted OpenTelemetry endpoints are monitored, with regular checks that each one is answering.
Because it's plain OTLP, your instrumentation stays portable: instrument once with OpenTelemetry, then search, chart and alert on that data in Logit.io alongside the rest of your observability data.
Key benefits
Every Logs stack gets an OTLP endpoint. It's not an add-on and not plan-gated.
Works with OpenTelemetry Collector Contrib and OpenTelemetry SDKs over OTLP/HTTP. No Logit agent.
Onboarding gives you copy-paste setup filled in with your stack's endpoint and credentials.
Endpoints are monitored, with regular checks that they're answering.
Frequently asked questions
Is Hosted OpenTelemetry included on every plan?
Yes. Every Logs stack gets a Hosted OpenTelemetry endpoint on every plan. It isn't an add-on.
Does it support gRPC?
No. Send OTLP over HTTP (http/protobuf) to https://{stackId}-otel.logit.io on port 443. gRPC isn't supported.
I already have a Logs stack. How do I get an endpoint?
Existing Logs stacks are opt-in: an account owner or administrator, or a stack administrator, selects Switch on in the Hosted OpenTelemetry card on the stack's Endpoints page. Setup takes a few minutes.
What happens to traces or metrics if I don't have an APM or Metrics stack?
The endpoint accepts them, but that data is dropped. Traces need an APM stack and metrics need a Metrics stack. Logs are always stored in your Logs stack.
Do I need a Logit.io agent?
No. Use OpenTelemetry Collector Contrib (otelcol-contrib), which includes the Basic auth extension, or any OpenTelemetry SDK that exports OTLP over HTTP.
Companies feel the difference when they use Logit.io
“One thing is certain when operating in the startup space, a strict budget. Before we make any purchase decision to use a SaaS Log Management platform, we need to validate the benefits of the platform and more importantly the team behind the platform.”
“Logit.io's customer support team stood out. Right from the beginning, the Logit.io team was there to answer questions and walk us through the process.”
Start your 14-day free trial
No credit card required. Logs from $25/mo.