-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add per-input metrics to libbeat pipeline client
Aggregates per-input metrics in libbeat/publisher/pipeline.client. New metrics: `events_pipeline_total`, `events_pipeline_filtered_total`, and `events_pipeline_published_total`. v2.Context includes a metric registry for context-specific metrics, created under `beat.Info.Monitoring.Namespace` and named after the context ID. If the context lacks an ID, a 'discard' metric registry, associated with no namespace, is used, preventing metric publication. v2.Input passes the v2.Context metric registry when creating the pipeline client. Introduces a new `inputmon` API, enabling inputs to publish their metrics via the HTTP monitoring endpoint, replacing the now deprecated `inputmon.NewInputRegistry`. Inputs must still register metrics using `inputmon.RegisterMetrics` for them to be published, and call `inputmon.UnregisterMetrics` to release resources on close. The deprecated `inputmon.NewInputRegistry` remains functional. Integration tests added for `filestream`, `httpjson`, and `cel` to verify new metrics.
- Loading branch information
Showing
23 changed files
with
1,042 additions
and
148 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
Oops, something went wrong.