You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Which problem is this PR solving?
- Prepare for 2.9.2 release
## Short description of the changes
- generated metrics doc
- updated changelog and release_note
Copy file name to clipboardexpand all lines: RELEASE_NOTES.md
+7-1
Original file line number
Diff line number
Diff line change
@@ -2,10 +2,16 @@
2
2
3
3
While [CHANGELOG.md](./CHANGELOG.md) contains detailed documentation and links to all the source code changes in a given release, this document is intended to be aimed at a more comprehensible version of the contents of the release from the point of view of users of Refinery.
4
4
5
+
## Version 2.9.2
6
+
7
+
Honeycomb's backend can now accept events with sizes up to 1 million bytes. This release enables Refinery to conform to the same limit and supports sending events up to 1MB.
8
+
It also improves Refinery's internal metrics by introducing a new metric, `incoming_router_otlp`, to track the amount of OTLP requests Refinery has received.
9
+
5
10
## Version 2.9.1
6
11
7
12
This is a bug fix release and includes the following changes:
8
-
* Registers all metrics during process start up to ensure they record their initial and ongoing values
13
+
14
+
- Registers all metrics during process start up to ensure they record their initial and ongoing values
Copy file name to clipboardexpand all lines: metrics.md
+6-1
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# Honeycomb Refinery Metrics Documentation
2
2
3
3
This document contains the description of various metrics used in Refinery.
4
-
It was automatically generated on 2024-12-02 at 18:38:37 UTC.
4
+
It was automatically generated on 2025-01-23 at 16:59:37 UTC.
5
5
6
6
Note: This document does not include metrics defined in the dynsampler-go dependency, as those metrics are generated dynamically at runtime. As a result, certain metrics may be missing or incomplete in this document, but they will still be available during execution with their full names.
7
7
@@ -14,6 +14,8 @@ This table includes metrics with fully defined names.
14
14
| cuckoo_current_capacity | Gauge | Dimensionless | current capacity of the cuckoo filter |
15
15
| cuckoo_future_load_factor | Gauge | Percent | the fraction of slots occupied in the future cuckoo filter |
16
16
| cuckoo_current_load_factor | Gauge | Percent | the fraction of slots occupied in the current cuckoo filter |
17
+
| cuckoo_addqueue_full | Counter | Dimensionless | the number of times the add queue was full and a drop decision was dropped |
18
+
| cuckoo_addqueue_locktime_uS | Histogram | Microseconds | the time spent holding the add queue lock |
17
19
| cache_recent_dropped_traces | Gauge | Dimensionless | the current size of the most recent dropped trace cache |
18
20
| collect_sent_reasons_cache_entries | Histogram | Dimensionless | Number of entries in the sent reasons cache |
19
21
| is_ready | Gauge | Dimensionless | Whether the system is ready to receive traffic |
@@ -58,6 +60,7 @@ This table includes metrics with fully defined names.
58
60
| trace_aggregate_sample_rate | Histogram | Dimensionless | aggregate sample rate of both kept and dropped traces |
59
61
| collector_redistribute_traces_duration_ms | Histogram | Milliseconds | duration of redistributing traces to peers |
60
62
| collector_collect_loop_duration_ms | Histogram | Milliseconds | duration of the collect loop, the primary event processing goroutine |
63
+
| collector_send_expired_traces_in_cache_dur_ms | Histogram | Milliseconds | duration of sending expired traces in cache |
61
64
| collector_outgoing_queue | Histogram | Dimensionless | number of traces waiting to be send to upstream |
62
65
| collector_drop_decision_batch_count | Histogram | Dimensionless | number of drop decisions sent in a batch |
63
66
| collector_expired_traces_missing_decisions | Gauge | Dimensionless | number of decision spans forwarded for expired traces missing trace decision |
@@ -97,6 +100,8 @@ Metrics in this table don't contain their expected prefixes. This is because the
97
100
|_router_dropped | Counter | Dimensionless | the number of events dropped because the channel was full |
98
101
|_router_nonspan | Counter | Dimensionless | the number of non-span events received |
99
102
|_router_peer | Counter | Dimensionless | the number of spans proxied to a peer |
103
+
|_router_batch | Counter | Dimensionless | the number of batches of events received |
104
+
|_router_otlp | Counter | Dimensionless | the number of batches of otlp requests received |
100
105
| queue_length | Gauge | Dimensionless | number of events waiting to be sent to destination |
101
106
| queue_overflow | Counter | Dimensionless | number of events dropped due to queue overflow |
102
107
| send_errors | Counter | Dimensionless | number of errors encountered while sending events to destination |
0 commit comments