You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
This adds a 90 day data retention limit for the elastic_agent.status_change data stream.
Prior to this change, this data stream did not have a retention limit set. Kibana has a task that writes to this elastic_agent.status_change every minute only if there is a change in status.
The primary use case for this data is for setting up alert rule monitoring of elastic agents. 90 days would allow users to analyze trends with status changes that may occur with an agent over the span of weeks or months. This also aligns with similar retention of our per 1m metric default policies for APM: https://www.elastic.co/docs/solutions/observability/apm/index-lifecycle-management.
@MichelLosier if this datastream only exist from 9.2 onwards, shouldn't we update the Kibana version constraint of this package?
The datastream exist as part of the elastic-agent package, so both the datastream definition and the template are contained in that version, and could be installed in kibana < 9.2
The datastream was already introduced in version 2.3.0 of this package, if we were to kibana version constraint this maybe a breaking change for the package.
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.
andrewkroh
added
Integration:elastic_agent
MichelLosier
force-pushed
the
add-data-retention-ea-status-change-logs
branch
from
Proposed commit message
Resolves: https://github.com/elastic/ingest-dev/issues/5692
This adds a 90 day data retention limit for the
elastic_agent.status_changedata stream.Prior to this change, this data stream did not have a retention limit set. Kibana has a task that writes to this
elastic_agent.status_changeevery minute only if there is a change in status.The primary use case for this data is for setting up alert rule monitoring of elastic agents. 90 days would allow users to analyze trends with status changes that may occur with an agent over the span of weeks or months. This also aligns with similar retention of our per 1m metric default policies for APM: https://www.elastic.co/docs/solutions/observability/apm/index-lifecycle-management.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots