Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[8.x](backport #42514) Write latency statistics go under a histogram key #42527

Merged
merged 3 commits into from
Jan 31, 2025
Merged

[8.x](backport #42514) Write latency statistics go under a histogram key #42527

merged 3 commits into from
Jan 31, 2025
+218 −5

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jan 31, 2025

follow-on from #42439

  1. write latency goes under a histogram key
  2. Fix broken metricbeat Integration tests caused by Include full queue metrics in the monitoring index #42439

Closes #42520

This is an automatic backport of pull request #42514 done by Mergify.

@strawgate @mergify
Write latency statistics go under a histogram key (#42514)
9eb62df 
* Write latency goes under histogram

* Update fields.yml to include new exposed beats stats

* Add't updates for integ tests

---------

Co-authored-by: Julien Lind <[email protected]>
(cherry picked from commit 0ff52eb)

# Conflicts:
#	metricbeat/module/beat/stats/data.go
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Jan 31, 2025
@mergify mergify bot requested a review from a team as a code owner January 31, 2025 08:00
@mergify Mergify
Copy link
Contributor Author

mergify bot commented Jan 31, 2025

Cherry-pick of 0ff52eb has failed:

On branch mergify/bp/8.x/pr-42514
Your branch is up to date with 'origin/8.x'.

You are currently cherry-picking commit 0ff52ebd4.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   metricbeat/docs/fields.asciidoc
	modified:   metricbeat/module/beat/fields.go
	modified:   metricbeat/module/beat/stats/_meta/fields.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   metricbeat/module/beat/stats/data.go

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jan 31, 2025
@github-actions github-actions bot added the Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team label Jan 31, 2025
@elasticmachine
Copy link
Collaborator

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jan 31, 2025
@strawgate strawgate enabled auto-merge (squash) January 31, 2025 14:32
@strawgate strawgate merged commit 57aeae6 into 8.x Jan 31, 2025
32 checks passed
@strawgate strawgate deleted the mergify/bp/8.x/pr-42514 branch January 31, 2025 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@strawgate strawgate

Labels
backport conflicts There is a conflict in the backported pull request Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@elasticmachine @strawgate