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
Copy file name to clipboardexpand all lines: website/content/en/highlights/2023-07-05-0-31-0-upgrade-guide.md
+13-1
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
date: "2023-07-05"
3
3
title: "0.31 Upgrade Guide"
4
4
description: "An upgrade guide that addresses breaking changes in 0.31.0"
5
-
authors: ["tobz"]
5
+
authors: ["stephenwakely", "tobz"]
6
6
release: "0.31.0"
7
7
hide_on_release_notes: false
8
8
badges:
@@ -12,6 +12,7 @@ badges:
12
12
Vector's 0.31.0 release includes **breaking changes**:
13
13
14
14
1.[Removal of various deprecated internal metrics](#deprecated-internal-metrics)
15
+
1.[`component_received_event_bytes_total` and `component_sent_event_bytes_total` consistently use estimated JSON size of the event](#event_json_size)
15
16
16
17
We cover them below to help you upgrade quickly:
17
18
@@ -49,3 +50,14 @@ A small note is that a small number of components still emit some of these metri
49
50
additional tags and information that is disallowed by the Component Specification. They will be
50
51
removed in a future version once we can rectify those discrepancies, but they are effectively
51
52
removed as of this release: you cannot depend on them still existing.
53
+
54
+
#### `component_received_event_bytes_total` and `component_sent_event_bytes_total` consistently use estimated JSON size of the event {#event_json_size}
55
+
56
+
Prior to this Version, metrics emitted by Vector were inconsistently measuring
57
+
the byte size of the events that were being sent and received. These metrics
58
+
have been updated for all components so they always emit an estimate of the size
59
+
of the event should it be serialized to JSON.
60
+
61
+
Measuring the events like this allows a consistent measurement to be applied
62
+
across all components regardless of how the source or sink serializes the event
0 commit comments