Automation
Ship spend and token metrics into New Relic over OTLP, with EU and US endpoints.
Lineman pushes your AI-coding spend, savings and token counts into New Relic as OTLP metrics, so cost sits on the same dashboards as the rest of your engineering telemetry. Company totals arrive alongside per-developer and per-repository breakdowns, and the export runs every 15 minutes. Metrics are sent as delta, authenticated with the api-key header and a New Relic licence key. US accounts use https://otlp.nr-data.net and EU accounts use https://otlp.eu01.nr-data.net.
Chart lineman.spend, lineman.savings and lineman.tokens in New Relic next to your service metrics. Money is in USD. Token series carry a token.type label of input, output or cache. Each run exports everything since the last push New Relic accepted, so a failed run loses nothing and the next one covers a wider window.
Alongside company totals, Lineman exports spend split by developer email and by repository, as lineman.spend.by_developer and lineman.spend.by_repo. Both are capped at the 100 highest-spending developers and the 100 highest-spending repositories, which keeps the payload inside the destination's limit. You can see which repositories and which people drive the bill without anyone compiling a report.
EU accounts take https://otlp.eu01.nr-data.net and US accounts take https://otlp.nr-data.net. Paste the endpoint your New Relic account gives you, with a licence key rather than a user key. Either a base URL or a full /v1/metrics URL works, because Lineman adds the signal path only when it is missing. 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 instead of leaving a dashboard quietly empty.
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