Repository navigation
Show each pipeline's throughput on every dashboard - #36
Merged
Merged
Conversation
zzylol
force-pushed
the
feat/hh-accuracy
branch
from
October 19, 2026 17:33
ae8d902 to
f0b5fe4
Compare
zzylol
force-pushed
the
feat/pipeline-throughput
branch
from
October 19, 2026 17:33
7ea370f to
80f9c3e
Compare
zzylol
force-pushed
the
feat/hh-accuracy
branch
from
October 19, 2026 20:15
f0b5fe4 to
bffc387
Compare
zzylol
force-pushed
the
feat/pipeline-throughput
branch
2 times, most recently
from
October 19, 2026 20:16
ed62bb0 to
b55694e
Compare
zzylol
force-pushed
the
feat/hh-accuracy
branch
from
October 19, 2026 20:16
bffc387 to
986f1cb
Compare
zzylol
force-pushed
the
feat/pipeline-throughput
branch
from
October 19, 2026 20:16
b55694e to
f87cc59
Compare
zzylol
force-pushed
the
feat/hh-accuracy
branch
from
October 19, 2026 20:16
986f1cb to
bb9b0c5
Compare
zzylol
force-pushed
the
feat/pipeline-throughput
branch
from
October 19, 2026 20:16
f87cc59 to
644d514
Compare
zzylol
force-pushed
the
feat/hh-accuracy
branch
2 times, most recently
from
October 19, 2026 20:17
3dc60b9 to
a97a269
Compare
zzylol
force-pushed
the
feat/pipeline-throughput
branch
2 times, most recently
from
October 19, 2026 20:17
038a6a0 to
e6235c9
Compare
zzylol
force-pushed
the
feat/hh-accuracy
branch
2 times, most recently
from
October 19, 2026 20:18
10782f4 to
f7bb4ba
Compare
zzylol
force-pushed
the
feat/pipeline-throughput
branch
2 times, most recently
from
October 19, 2026 20:18
0a069ea to
b8d6c9f
Compare
zzylol
force-pushed
the
feat/hh-accuracy
branch
from
October 19, 2026 20:18
f7bb4ba to
70f9686
Compare
zzylol
force-pushed
the
feat/pipeline-throughput
branch
from
October 19, 2026 20:18
b8d6c9f to
ac01ae2
Compare
zzylol
force-pushed
the
feat/hh-accuracy
branch
from
October 19, 2026 20:18
70f9686 to
2d4a81f
Compare
zzylol
force-pushed
the
feat/pipeline-throughput
branch
2 times, most recently
from
October 19, 2026 20:19
e9931c2 to
86fd69c
Compare
zzylol
force-pushed
the
feat/hh-accuracy
branch
2 times, most recently
from
October 20, 2026 23:24
5aba1b9 to
139e72a
Compare
zzylol
force-pushed
the
feat/pipeline-throughput
branch
from
October 20, 2026 23:24
86fd69c to
69e0727
Compare
zzylol
force-pushed
the
feat/pipeline-throughput
branch
from
October 20, 2026 23:38
69e0727 to
f5ba2ad
Compare
zzylol
force-pushed
the
feat/hh-accuracy
branch
from
October 20, 2026 23:38
139e72a to
8383a6e
Compare
The engine counts messages and bytes, not data points, so the panel uses asap_points: the points each 1-minute window delivered to the end of its pipeline (sketch and exact: the points their detector answered for; raw: the points loki-raw acknowledged), divided by 60 s, against the offered 2 x 20,000 points/s.
zzylol
force-pushed
the
feat/pipeline-throughput
branch
from
October 20, 2026 23:38
f5ba2ad to
edad787
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part 13 of the telemetry-functions stack: a throughput panel per pipeline on every dashboard.
Why
The dashboards showed each pipeline's delay, CPU, bytes and memory, but not how many points per second it actually gets through. That is the number that shows the raw pipeline falling behind.
What
A panel "Throughput per pipeline" on the latency, cardinality, drift and top-k dashboards: points per second that each 1-minute window delivered to the end of its pipeline, with the offered 2 × 20,000 points/s as a dashed line.
sum by (method) (asap_points{...}) / 60, the points the detector answered for (summed over the use case's series, e.g. per route for latency; thehttp.routekey for the per-attribute use cases).asap_points{method="raw"} / 60, the pointsloki-rawacknowledged.The engine's own telemetry counts messages, requests and bytes but not data points, so there is no per-second counter; this is one value per window.
Result (live top-k demo, 56-core x86 server)
sketch 40,000 points/s and exact 40,000 points/s, the full offered rate; raw 32,458 points/s:
loki-rawstores fewer points per window than offered.Verification
Both queries evaluated against the live demo's Prometheus (values above); the dashboards reloaded in Grafana with the new panel. Dashboard JSON and README only.