Founder of @openlit_io | Cyber security using AI @transilienceai https://xitter.cf/t.co/cz5Dr0pbHj

Noida
Joined August 2014
If you’re building agents and want @openlit_io in the loop, DM me or email [email protected] Feature idea → same, or github.com/openlit/openlit/i… Collab → connect and we’ll work something out Enterprise beta / trial → reach out, we’re taking users
1
18
CVE-2026-85046 Google Chrome V8 Type Confusion Zero-Day 🚨 A webpage visit can be enough to exploit CVE-2026-85046. The actively exploited V8 type confusion flaw enables sandboxed code execution in Chrome and affects the broader Chromium ecosystem. Patch to 152.0.7977.82/.83+, restart, then hunt for suspicious browser-spawned processes and outbound connections.
2
2
3
119
Aman Agarwal retweeted
Your stack already has a home for telemetry. OpenLIT datasource connectors let you bring it in: ClickHouse · Tempo · Loki · Prometheus · Jaeger Per-environment signal routing for traces, logs, and metrics. Docs: docs.openlit.io/latest/openl… OpenPlait: npmjs.com/settings/openplait…
2
1
1
68
Your stack already has a home for telemetry. OpenLIT datasource connectors let you bring it in: ClickHouse · Tempo · Loki · Prometheus · Jaeger Per-environment signal routing for traces, logs, and metrics. Docs: docs.openlit.io/latest/openl… OpenPlait: npmjs.com/settings/openplait…
2
1
1
68
Most AI teams don’t need another telemetry silo. They need OpenLIT to read the backends they already run. Datasource connectors + signal routing are live 🧵
24
GPU utilization is a vanity metric for LLM inference. nvidia-smi and DCGM tell you the SM was busy. Not KV cache OOM, throttle, or zombie VRAM. What to SLO instead: openlit.io/blogs/gpu-util-is…
1
1
33
Most #LLM #observability guides stop at a single chat completion. But production AI systems are far more complex. This post is a joint effort by the OpenLIT and VictoriaMetrics teams. @openlit_io brings the #OpenTelemetry-native instrumentation for LLMs and agents, while VictoriaMetrics provides the storage and query layer for the resulting metrics, traces, and logs. We wrote it together to show how the two projects fit into a single, self-hosted observability pipeline, and to share the patterns and queries that worked well for us along the way. Learn more 👇 hubs.ly/Q04nFzRY0 #Otel #OpenLIT #SDK VictoriaMetrics
4
6
394
6/6 Best part? OpenLIT is OpenTelemetry-native and self-hosted. Otter runs entirely within your private network—no data leaks.
53
5/6 🔒 Private VPC Compliance: Since OpenLIT is self-hosted, Otter analyzes telemetry logs locally, meeting HIPAA/GDPR constraints without leaking data to external APIs.
28
4/6 💸 Custom Pricing: Register token pricing for local models (Ollama/vLLM) so local cluster costs show up accurately alongside public cloud API costs.
26
3/6 🛡️ Query by Attribute: Ask Otter to retrieve traces matching any attribute you capture (session ID, custom safety tags) and it writes the ClickHouse query for you—then helps you draft a Rule Engine condition from what it finds.
40
2/6 🤖 Trace Analysis: Otter's routing/execution-path review flags repetitive tool calls in LangGraph/CrewAI traces and explains what likely caused them.
39
I wrote about a hard truth in RAG: 👉 Retrieval doesn’t eliminate hallucinations. Even with good context, models can still give wrong answers. In this blog: * Where hallucinations come from * Why retrieval isn’t enough (Dont trust the model!) 🔗 openlit.io/blogs/how-to-dete…
1
2
50
Been working with LLM systems lately and one thing stands out: We track latency, tokens, cost… but barely look at the GPU. which is where all the work happens. Most debugging pain I’ve hit comes from this gap. I wrote this blog to connect the dots: openlit.io/blogs/gpu-monitor…
1
3
47