Otelic is built on top of OpenTelemetry. OpenTelemetry is market's default way to instrument code.
Just follow official Open Telemetry guides for Kubernetes. In Kubernetes setup usually you would deploy Open Telemetry Collector inside Kubernetes cluster as one of the pods.
Logs exporter endpoint:
https://ingest.otelic.com/otel/v1/logs
Traces exporter endpoint:
https://ingest.otelic.com/otel/v1/traces
Set API key with header:
x-api-key get for free in workspace settings
Inside Collector's yaml config, these are key configuration properties to send traces & logs to Otelic:
1exporters:
2 otlphttp/traces:
3 endpoint: "https://ingest.otelic.com/otel"
4 headers:
5 x-api-key: "YOUR_FREE_API_KEY"
6 otlphttp/logs:
7 endpoint: "https://ingest.otelic.com/otel"
8 headers:
9 x-api-key: "YOUR_FREE_API_KEY"
10
11service:
12 pipelines:
13 traces:
14 receivers: [otlp]
15 processors: [transform, batch]
16 exporters: [otlphttp/traces]
17 logs:
18 receivers: [otlp]
19 processors: [batch]
20 exporters: [otlphttp/logs]Resolve your LOGS & TRACES issues within minutes
Developer-friendlyquick setup
gRPC & HTTPS support out of the box
Just add Otelic to yourOpenTelemetry collector
Otelic.com is built on top of the open-source market's best tooling for logs & traces: Open Telemetry. Just follow the OpenTelemetry guides and point your logs & traces exporters to Otelic endpoints, using the x-api-key header to authorize requests. Otelic supports various languages and platforms, including JavaScript, C++, C#, .NET, Erlang, Go, Java, PHP, Python, Ruby, Rust, and Swift. It supports standalone deployments, serverless environments, Dockerized setups, Kubernetes, and more.
