No collectors to operate, no query language to learn. Instrument once, and SentriNode handles ingestion, analysis, prediction, and the fix.
Five things happen between your first span and a fix. Here is each one. The numbers in the pictures are illustrative.
Add the SDK for Python or Node, or point any OpenTelemetry client at the endpoint. Every LLM call starts streaming: model, tokens, latency and cost.
Spans land at the ingest and feed a real-time engine. It recomputes percentiles, error rates and per-model cost continuously, and watches every service for anomalies.
A trend forecast spots a latency breach coming, names the culprit service and gives an ETA, so you act while it is still a trend instead of an outage.
AI writes the root cause from the live anomaly, drafts a filled-in Jira ticket, and lists the exact diagnostic commands to run.
llm-proxy p95 rose 203% after retries to the upstream model began stacking behind a saturated connection pool.
Set a monthly LLM budget and get alerted at your threshold. With the hard cap on, the SDK refuses calls once you are over, instead of reporting it after the bill.
Replay any incident like a recording. Scrub the timeline and watch the latency spike and the failure cascade as it happened.
Model a traffic spike, extra latency or more capacity against your real baseline, and see the projected impact and cost.
Recommendations on what to sample or drop, with savings estimates, so you ingest only what is worth paying for.
SentriNode reads OpenTelemetry GenAI spans, so anything already emitting them works without adopting our SDK. Costs are computed server-side from the model and token counts — you do not have to send a price.
LangChain, LlamaIndex, OpenLLMetry, Traceloop, LiteLLM and the Vercel AI SDK all spell these attributes differently. All of them are read.
Anthropic, OpenAI, Google, Meta Llama, Mistral, Cohere, DeepSeek and xAI — including provider-prefixed ids from OpenRouter and Bedrock. Override any price without a redeploy.
Point an OpenTelemetry Collector at the same endpoint for CPU, memory, disk and network. Works on Linux, macOS and Windows.
Setup instructions → Limits & throughput
An unknown model still records tokens and latency — it is reported as unpriced rather than free, so nothing silently reads as zero.