Operations | Monitoring | ITSM | DevOps | Cloud

Learn how to trace complex multi-hop transactions across microservices when OpenTelemetry isn't available or trace parents get lost. This quick tutorial demonstrates how to use full-text search in proxymock (a free CLI and UI tool) to isolate user journeys (like looking up a specific username) and instantly generate waterfall tracing views. Whether you are working locally or in a Kubernetes cluster, you can record API traffic, visualize multi-hop requests, and easily transition those captures into load or regression tests.

This video explains how to trace a user through older or inaccessible services using identifiable information like emails or usernames when OpenTelemetry traces are unavailable.

At any given moment, your AI systems can be down, slow, overloaded, or just returning bad results. Someone's gotta babysit the bots. Sentry traces across your AI pipeline, from user request to final response, so you can see exactly what's happening and fix it.

In this tutorial you'll learn how to use Uptrace and Grafana together. Uptrace exposes a Prometheus-compatible HTTP endpoint, so you can add it as a data source in Grafana and reuse your existing dashboards without changing metric names or rewriting queries.

Learn the two main ways to get data into Grafana Cloud. In this video, we break down how Grafana Cloud connects to over 150 external data sources (like Salesforce, Postgres, and CloudWatch) where your data stays in place, and how you can send raw telemetry into Grafana’s fully managed databases for logs, metrics, traces, and profiles.

Telemetry Talks explores how OpenTelemetry’s CNCF graduation arrives at a pivotal moment for AI-powered development. Together with Alex Marshalov, we dive into vibe coding, AI agents, and the growing need for observability in GenAI systems — from prompts and token usage to reasoning chains and distributed traces — using the VictoriaMetrics stack and OpenTelemetry as the foundation for understanding the next generation of autonomous software.

A semantic-convention rename (http.method → http.request.method) can silently break your RED metrics — no errors, just gaps in dashboards and alerts. The OpenTelemetry Collector's schema processor fixes it: put it first in your pipeline and it normalizes attribute names no matter what each service emits. Migration mode writes BOTH the old and new names, so you get zero-downtime upgrades while queries keep working.