Commit cb6b7d4
hubble: count ring-buffer lost events on forward reads only
The `hubble_ring_buffer` lost events metric was incremented whenever
a reader reached the ring buffer boundary. However, reaching the
boundary does not always mean events were actually lost. Hitting the
boundary in backward scans is an expected stop condition rather than
a real loss.
This commit moves the metric count from the producer (ring.getLostEvent)
to the consumer's forward-reading paths (RingReader.Next/NextFollow).
The metric is now counted only when a consumer actually catches a lost
event. Normal ring scans no longer count the metric when they expectedly
reach that boundary.
Fixes: cilium#46584
Signed-off-by: Tomoki Sugiura <tomoki-sugiura@cybozu.co.jp>1 parent dbd7ebc commit cb6b7d4
2 files changed
Lines changed: 11 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
7 | 7 | | |
8 | 8 | | |
9 | 9 | | |
10 | | - | |
11 | 10 | | |
12 | 11 | | |
13 | 12 | | |
| |||
16 | 15 | | |
17 | 16 | | |
18 | 17 | | |
19 | | - | |
20 | 18 | | |
21 | 19 | | |
22 | 20 | | |
| |||
217 | 215 | | |
218 | 216 | | |
219 | 217 | | |
220 | | - | |
221 | 218 | | |
222 | 219 | | |
223 | 220 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
5 | 5 | | |
6 | 6 | | |
7 | 7 | | |
| 8 | + | |
8 | 9 | | |
9 | 10 | | |
| 11 | + | |
10 | 12 | | |
| 13 | + | |
11 | 14 | | |
12 | 15 | | |
13 | 16 | | |
| |||
67 | 70 | | |
68 | 71 | | |
69 | 72 | | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
70 | 77 | | |
71 | 78 | | |
72 | 79 | | |
| |||
115 | 122 | | |
116 | 123 | | |
117 | 124 | | |
| 125 | + | |
| 126 | + | |
| 127 | + | |
| 128 | + | |
118 | 129 | | |
119 | 130 | | |
120 | 131 | | |
| |||
0 commit comments