Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on Distributed Tracing and related technologies.

Introducing Fine-Grained RBAC: Resource-Level Permissions in SigNoz

A quick demo of fine-grained access control in SigNoz, using dashboards as the example. We’ve built one of the most advanced access control models in the observability space. See how to define exactly who can access each individual dashboard.

We Upgraded SigNoz Infrastructure Monitoring for Deeper Visibility and Faster Troubleshooting

A quick walkthrough of the new infrastructure monitoring experience in SigNoz Cloud. We’ve made several additions to give you more visibility into your infrastructure health and help you troubleshoot faster. Here’s what’s new,

Sentry JavaScript SDK v11 adds tracing for all JS platforms

This post is about a recent change to the Sentry JavaScript SDKs. If you don’t use Sentry with JavaScript, it may still be useful as a look at how we made the change and why. In the Sentry JavaScript SDK v11, we rebuilt how our tracing integrations work. While we still support the OpenTelemetry standard (described in more detail below), we now instrument your dependencies with a code transformer instead of using the OpenTelemetry instrumentation classes as we did in previous versions.

Manage your OpenTelemetry Collectors with Fleet Management in Grafana Cloud

If you’ve built your telemetry pipelines around OpenTelemetry Collectors, you’ve already invested in a collector distribution, YAML configuration, and a deployment model that fits your infrastructure. As that deployment grows, managing it means keeping shared configuration consistent, accommodating different workloads, and understanding whether your collectors are healthy. Fleet Management in Grafana Cloud brings those tasks together in one place.

OpenTelemetry Collector Configuration for LLM Observability

Your LLM application emits telemetry unlike anything else in your stack. Model calls, tool invocations, retrieval steps, and token usage arrive as spans whose attributes carry entire prompts and completions. That data is bulky, it's full of user content you may not be allowed to export, and depending on which instrumentation each service uses, the same fact can arrive under different attribute names.