[MetricBeat][StackMonitoring] fetching index summary from node/_stats endpoint#45049
Merged
[MetricBeat][StackMonitoring] fetching index summary from node/_stats endpoint#45049
Conversation
botelastic
Bot
added
the
needs_team
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as resolved.
This comment was marked as resolved.
botelastic
Bot
removed
the
needs_team
filippomachi
added
the
backport-active-all
pickypg
approved these changes
Jul 4, 2025
Member
pickypg
left a comment
pickypg
left a comment
There was a problem hiding this comment.
LGTM. This should be a notable improvement over the old approach for users that do a lot of index deletion.
Contributor
|
@Mergifyio backport 8.17 8.18 8.19 9.0 9.1 |
Contributor
✅ Backports have been createdDetails
|
mergify Bot
pushed a commit
that referenced
this pull request
Jul 4, 2025
… 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)
6 tasks
mergify Bot
pushed a commit
that referenced
this pull request
Jul 4, 2025
… 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)
6 tasks
mergify Bot
pushed a commit
that referenced
this pull request
Jul 4, 2025
… 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)
6 tasks
mergify Bot
pushed a commit
that referenced
this pull request
Jul 4, 2025
… 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) # Conflicts: # metricbeat/module/elasticsearch/index_summary/index_summary.go
6 tasks
mergify Bot
pushed a commit
that referenced
this pull request
Jul 4, 2025
… 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)
6 tasks
pickypg
pushed a commit
that referenced
this pull request
Jul 4, 2025
… endpoint (#45049) (#45204) 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) Co-authored-by: filippomachi <filippo.machi@elastic.co>
pickypg
pushed a commit
that referenced
this pull request
Jul 4, 2025
… endpoint (#45049) (#45200) 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) Co-authored-by: filippomachi <filippo.machi@elastic.co>
pickypg
added a commit
that referenced
this pull request
Jul 4, 2025
…ummary from node/_stats endpoint (#45203) * [MetricBeat][StackMonitoring] fetching index summary from node/_stats 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) # Conflicts: # metricbeat/module/elasticsearch/index_summary/index_summary.go * Fix merge conflict (accept new changes exclusively) --------- Co-authored-by: filippomachi <filippo.machi@elastic.co> Co-authored-by: Chris Earle <pickypg@gmail.com>
pickypg
pushed a commit
that referenced
this pull request
Jul 4, 2025
… endpoint (#45049) (#45201) 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) Co-authored-by: filippomachi <filippo.machi@elastic.co>
pickypg
pushed a commit
that referenced
this pull request
Jul 4, 2025
… endpoint (#45049) (#45202) 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) Co-authored-by: filippomachi <filippo.machi@elastic.co>
6 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Proposed commit message
Fetching index summary metricset from node/_stats endpoint
Please explain:
Checklist
CHANGELOG.next.asciidocorCHANGELOG-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