forked from vectordotdev/vector
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore(observability): remove more deprecated internal metrics (vector…
…dotdev#17542) This is a follow-up PR to vectordotdev#17516, which does a few things: - completely removes `processing_errors_total`, `events_failed_total`, and `events_discarded_total`, with one exception (see reviewer notes) - adds a 0.31 upgrade guide which covers the removal of these metrics and the metrics removed in vectordotdev#17516 - updates the Cue files for all components to derive their Component Specification-related metrics descriptions at the component type level (see reviewer notes) ## Reviewer Notes ### One dangling reference to `events_discarded_total` There's still one dangling reference to this deprecated metric for the `throttle` transform. I left a TODO comment in the code, but essentially, it currently specifies a tag (which bucket key was throttled) for `events_discarded_total` which can't be translated directly to `component_discarded_events_total` as the specification disallows custom tags. We'll probably need to quickly talk about whether the specification is too rigid or if we actually want to emit that tag at all. ### Updated Cue files for common component metrics I followed the Component Specification here, since technically all components receive and send events, and can drop or discard those events. This touched a vast majority of the component Cue files, and should bring them up to a far more consistent state than the previous set of circumstances. There's definitely something to be said for even pushing up the abstraction of how components inherit that `telemetry: metrics { ... }` stuff so it's driven by component type rather than hard-coded in the per-component-type Cue file (`sources.cue`, etc)... but this felt like a reasonable middle ground to leave it at for now.
- Loading branch information
Showing
111 changed files
with
216 additions
and
649 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
51 changes: 51 additions & 0 deletions
51
website/content/en/highlights/2023-07-05-0-31-0-upgrade-guide.md
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,51 @@ | ||
--- | ||
date: "2023-07-05" | ||
title: "0.31 Upgrade Guide" | ||
description: "An upgrade guide that addresses breaking changes in 0.31.0" | ||
authors: ["tobz"] | ||
release: "0.31.0" | ||
hide_on_release_notes: false | ||
badges: | ||
type: breaking change | ||
--- | ||
|
||
Vector's 0.31.0 release includes **breaking changes**: | ||
|
||
1. [Removal of various deprecated internal metrics](#deprecated-internal-metrics) | ||
|
||
We cover them below to help you upgrade quickly: | ||
|
||
## Upgrade guide | ||
|
||
### Breaking changes | ||
|
||
#### Removal of various deprecated internal metrics {#deprecated-internal-metrics} | ||
|
||
Over the course of many of the previous releases, we've been working to deprecate the usage of older | ||
internal metrics as we worked towards implementing full support for the [Component | ||
Specification][component_spec], which dictates the basic metrics that all components, or the basic | ||
metrics all components of a specific type, are expected to emit. | ||
|
||
We've made enough progress on this work that we've gone ahead and removed many of the deprecated | ||
metrics from this release. First, below is a list of all metrics we've removed: | ||
|
||
- `events_in_total` (superceded by `component_received_events_total`) | ||
- `events_out_total` (superceded by `component_sent_events_total`) | ||
- `processed_bytes_total` (superceded by either `component_received_bytes_total` or | ||
`component_sent_bytes_total`, more below) | ||
- `processed_events_total` (superceded by either `component_received_events_total` or | ||
`component_sent_events_total`, more below) | ||
- `processing_errors_total` (superceded by `component_errors_total`) | ||
- `events_failed_total` (superceded by `component_errors_total`) | ||
|
||
Most of the removals have straightforward replacements, but the `processed_`-prefixed metrics | ||
involve a small amount of logic. For **sources**, `processed_bytes_total` is superceded by | ||
`component_received_bytes_total`, and `processed_events_total` is superceded by | ||
`component_received_events_total`. For **sinks**, `processed_bytes_total` is superceded by | ||
`component_sent_bytes_total`, and `processed_events_total` is superceded by | ||
`component_sent_events_total`. | ||
|
||
A small note is that a small number of components still emit some of these metrics, as they provided | ||
additional tags and information that is disallowed by the Component Specification. They will be | ||
removed in a future version once we can rectify those discrepancies, but they are effectively | ||
removed as of this release: you cannot depend on them still existing. |
This file contains 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
This file contains 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
Oops, something went wrong.