Automation
Ship spend and token metrics into Coralogix over OTLP, on your region's ingress host.
Put your AI-coding spend on the same Coralogix dashboards as the rest of your engineering telemetry. Lineman pushes spend, savings and token counts over OTLP to your region's Coralogix ingress host every 15 minutes, authenticated with a Send-Your-Data API key, with per-developer and per-repository breakdowns alongside the company totals. Coralogix takes delta metrics, and Lineman sets the temporality from the destination you pick rather than leaving the export to fail quietly at ingest.
Add lineman.spend and lineman.savings to the Coralogix dashboards your team already opens. AI-coding cost is then read next to your service telemetry instead of only in the Lineman dashboard. Send a test datapoint first: it pushes one real metric and reports the exact URL it reached, so a wrong endpoint shows up straight away.
lineman.spend.by_developer is labelled with each developer's email, and lineman.spend.by_repo splits the same spend by repository. Both are capped at the 100 highest spenders, which keeps the payload inside the destination's size limit so the company totals still get through.
Spend and token counts reach Coralogix every 15 minutes, so a change that made coding sessions more expensive shows up the same day rather than on next month's invoice. Each run exports everything since the last push Coralogix accepted, so a failed run loses nothing and the next one covers a wider window.
The documentation walks through connecting it, what Lineman reads and writes, and the settings worth knowing about.
Read the setup guideEvery integration in one place, searchable by name and filterable by what it does.
View all integrations