Per‑operation view of the service’s messaging / queue work (producers and consumers).
Get here: Service Overview → Messaging Systems tab.
What is Messaging System
It covers the service’s asynchronous queue work (transaction_category = Messaging queues) — publishing to and consuming from brokers such as Kafka, RabbitMQ, or SQS — the panel behind the Messaging Systems card on Service Overview. Because messaging is async, problems show up differently from web/DB: a slow or erroring consumer signals processing back‑pressure or lag, while a failing producer means messages aren’t being published. Split the view with the Kind filter (producer vs consumer) to tell the two apart, then use Most Time Consuming / Highest Error Rate to find the specific operation before checking a trace.
Charts (trace metrics — exact)
Four trend charts — Latency, Error Rate (non‑web), Throughput, and Most Time Consuming — track the service’s producer/consumer activity over the selected window.
Filters
The Kind filter (producer vs consumer) is unique to this panel and is usually the quickest way to split the two apart. You can also narrow by Infrastructure and Resource, or focus on one Messaging System sub‑category. Metric controls set the Error Code series (5.*) and Apdex Threshold (500 ms), and Compare / Range / Step change the time window and comparison.
Note: The Kind filter is often the quickest way to isolate a slow consumer from a fast producer (or vice versa).
Top 20 Operations
Ranked three ways; a Sub‑category column groups by messaging system, and the Kind filter splits producers vs consumers. All Operations opens the full list.
Most Time Consuming — which operations cost the most time?
- Operation / Sub‑category — the operation and system. Click to open the operation detail.
- Slowest Span — slowest sampled span (clickable); jump to a worst‑case example → waterfall.
- Overall Latency (Ms) — cumulative time consumed (latency × volume); highest = biggest total drain.
- Peak Avg Latency (Ms) — worst spike of the average; big gap vs. Avg = bursty (consumer back‑pressure).
- Avg Latency (Ms) — mean latency (baseline).
Highest Error Rate — which operations fail the most?
Operation / Sub‑category · Error Rate (%) (non‑web) — cross‑check throughput.
Highest Throughput — which operations carry the most messages?
Operation / Sub‑category · Throughput (RPM) — busiest producers/consumers; capacity and lag hotspots.
Operation detail → traces → waterfall
Click an operation → tiles + Segment Breakdown → View Traces → a span → waterfall.
Workflow
- Brush the Latency / Most Time Consuming chart to the window.
- Set Kind = consumer (or producer) and pick the Messaging System.
- Open Most Time Consuming / Highest Error Rate → identify the operation → click a trace.
Share permalink · Export CSV · Top 20 cap.