Arcline documentation
Arcline ingests telemetry from your infrastructure and applications, then lets you query, visualize, and alert on it through a unified platform. This guide covers installation, core concepts, and the public API.
Quick install
Install the Arcline CLI to manage collectors, dashboards, and alert rules from your terminal.
Send your first data
The easiest path is OpenTelemetry. Point your OTLP exporter to the regional endpoint and data appears in the explorer within seconds.
Metrics
Metrics are stored in a columnar time-series database with automatic rollups. Query with Arcline Query Language (AQL), a PromQL-compatible syntax.
Logs
Logs are parsed at the edge, indexed on high-cardinality dimensions, and retained according to your plan. Search with structured queries or free text.
Traces
Traces are stored as spans with references. Use the trace explorer to follow a request across services, or aggregate latency histograms by operation.
Alerting
Alerts are defined as rules evaluated continuously. Route notifications to Slack, PagerDuty, email, or a webhook.
API reference
Authentication
All API requests require an API key in the x-arcline-api-key header. Rotate keys from the workspace settings.
Endpoints
| Method | Path | Description |
|---|---|---|
| POST | /v1/ingest/otlp | OTLP metrics/logs/traces |
| GET | /v1/metrics/query | Query time-series data |
| POST | /v1/alerts/rules | Create or update alert rules |
| GET | /v1/status | Component health |
SDKs
Official SDKs are available for Go, Python, Node.js, Ruby, and Java. Community SDKs cover Rust and Elixir.