Skip to content

[8.19](backport #45049) [MetricBeat][StackMonitoring] fetching index summary from node/_stats endpoint#45202

Merged
pickypg merged 2 commits into8.19from
mergify/bp/8.19/pr-45049
Jul 4, 2025
Merged

[8.19](backport #45049) [MetricBeat][StackMonitoring] fetching index summary from node/_stats endpoint#45202
pickypg merged 2 commits into8.19from
mergify/bp/8.19/pr-45049

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify Bot commented Jul 4, 2025

Proposed commit message

Fetching index summary metricset from node/_stats endpoint

Please explain:

  • WHAT: changing the source of data for index summary metrics
  • WHY: the metrics obtained from the Elasticsearch _stats endpoint are based on individual indices, and may become inaccurate or unreliable if indices are deleted or closed.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

None

How to test this PR locally

integration tests have been improved
try metricbeat integration locally closing/deleting indexes

Related issues

This is an automatic backport of pull request #45049 done by [Mergify](https://mergify.com).

@filippomachi @mergify
[MetricBeat][StackMonitoring] fetching index summary from node/_stats…
766ec51 
… endpoint (#45049)

Fetching index summary metricset from `_nodes/stats` endpoint instead of `_stats` so that as indexes are deleted, the summary stats are not effectively lost during the next poll because nodes cache their data. Gaps can still appear in charts if nodes are restarted (as their cache is zeroed out).

(cherry picked from commit 63a537a)
@mergify mergify Bot added the backport label Jul 4, 2025
@mergify mergify Bot requested a review from a team as a code owner July 4, 2025 19:24
@botelastic botelastic Bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jul 4, 2025
@mergify mergify Bot mentioned this pull request Jul 4, 2025
Merged
6 tasks
@botelastic botelastic Bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Jul 4, 2025
@pickypg pickypg enabled auto-merge (squash) July 4, 2025 19:26
@pickypg pickypg merged commit 1f415ff into 8.19 Jul 4, 2025
46 checks passed
@pickypg pickypg deleted the mergify/bp/8.19/pr-45049 branch July 4, 2025 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@pickypg pickypg pickypg approved these changes

Assignees

@filippomachi filippomachi

Labels

backport bug Feature:Stack Monitoring Team:Monitoring Stack Monitoring team Team:Opex

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@pickypg @filippomachi