Include full queue metrics in the monitoring index #42439
Merged
Conversation
This file contains hidden or 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
faec
added
bug
Team:Elastic-Agent-Data-Plane
botelastic
bot
added
needs_team
Contributor
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
mauri870
approved these changes
Jan 29, 2025
pickypg
reviewed
Jan 29, 2025
Member
pickypg
left a comment
pickypg
left a comment
There was a problem hiding this comment.
I have some questions before approving for Stack Monitoring.
Contributor
Author
|
Note that I just added a few more fields under |
mergify bot
pushed a commit
that referenced
this pull request
Jan 29, 2025
Add queue metrics to the Metricbeat monitoring schema so they can be included in standard Agent dashboards. This is the Beats-side half of #42093. Affected metrics are: `added.{events, bytes}`, `consumed.{events, bytes}`, `removed.{events, bytes}`, and `filled.{events, bytes, pct}`, all within `monitoring.metrics.libbeat.pipeline.queue`. (cherry picked from commit 7eb2bdd)
6 tasks
Member
|
This change seems to have broken some of the metricbeat tests, because of the new metrics: |
Contributor
Contributor
|
@faec adding backport 8.18 label as the branch has been created right before this merge |
mergify bot
pushed a commit
that referenced
this pull request
Jan 31, 2025
Add queue metrics to the Metricbeat monitoring schema so they can be included in standard Agent dashboards. This is the Beats-side half of #42093. Affected metrics are: `added.{events, bytes}`, `consumed.{events, bytes}`, `removed.{events, bytes}`, and `filled.{events, bytes, pct}`, all within `monitoring.metrics.libbeat.pipeline.queue`. (cherry picked from commit 7eb2bdd)
6 tasks
mergify bot
pushed a commit
that referenced
this pull request
Jan 31, 2025
Add queue metrics to the Metricbeat monitoring schema so they can be included in standard Agent dashboards. This is the Beats-side half of #42093. Affected metrics are: `added.{events, bytes}`, `consumed.{events, bytes}`, `removed.{events, bytes}`, and `filled.{events, bytes, pct}`, all within `monitoring.metrics.libbeat.pipeline.queue`. (cherry picked from commit 7eb2bdd)
6 tasks
This was referenced Jan 31, 2025
jlind23
pushed a commit
that referenced
this pull request
Jan 31, 2025
Add queue metrics to the Metricbeat monitoring schema so they can be included in standard Agent dashboards. This is the Beats-side half of #42093. Affected metrics are: `added.{events, bytes}`, `consumed.{events, bytes}`, `removed.{events, bytes}`, and `filled.{events, bytes, pct}`, all within `monitoring.metrics.libbeat.pipeline.queue`. (cherry picked from commit 7eb2bdd) Co-authored-by: Fae Charlton <[email protected]>
jlind23
pushed a commit
that referenced
this pull request
Jan 31, 2025
Add queue metrics to the Metricbeat monitoring schema so they can be included in standard Agent dashboards. This is the Beats-side half of #42093. Affected metrics are: `added.{events, bytes}`, `consumed.{events, bytes}`, `removed.{events, bytes}`, and `filled.{events, bytes, pct}`, all within `monitoring.metrics.libbeat.pipeline.queue`. (cherry picked from commit 7eb2bdd) Co-authored-by: Fae Charlton <[email protected]>
faec
added a commit
that referenced
this pull request
Jan 31, 2025
Add queue metrics to the Metricbeat monitoring schema so they can be included in standard Agent dashboards. This is the Beats-side half of #42093. Affected metrics are: `added.{events, bytes}`, `consumed.{events, bytes}`, `removed.{events, bytes}`, and `filled.{events, bytes, pct}`, all within `monitoring.metrics.libbeat.pipeline.queue`. (cherry picked from commit 7eb2bdd) Co-authored-by: Fae Charlton <[email protected]>
This was referenced Jan 31, 2025
3 tasks
5 tasks
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add queue/output metrics to the Metricbeat monitoring schema so they can be included in standard Agent dashboards. This is the Beats-side half of #42093. Affected metrics are:
added.{events, bytes},consumed.{events, bytes},removed.{events, bytes}, andfilled.{events, bytes, pct}, all withinlibbeat.pipeline.queue, andlibbeat.output.write.latency.{count, max, median, p99}.Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.