-
Notifications
You must be signed in to change notification settings - Fork 524
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.
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
apmpackage: define DLM retention periods in apm package #11539
Conversation
This pull request does not have a backport label. Could you fix it @kyungeunni? 🙏
NOTE: |
This pull request is now in conflicts. Could you fix it @kyungeunni? 🙏
|
* feat: add DLM definitions for datastreams * chore: update elastic-package version * fix: update package format_version to 2.11.0 * chore: update CHANGELOGs
Assigning to myself for testing |
Looks good in serverless project. Here's a
ILM policies continue to be installed in stateful. |
Motivation/summary
Define DLM retention periods corresponding to the default ILM policy's
policy.delete.min_age
to support DLM when configured.Checklist
apmpackage
have been made)- [ ] Documentation has been updatedFor functional changes, consider:
How to test these changes
Run
tilt up
Open Kibana, go to Index Management > Index Template, and choose one of the templates APM server manages, for example:
metrics-apm.service_summary.1m
Check the lifecycle is pointing to the ILM policy
Run
tilt down
, addxpack.fleet.internal.disableILMPolicies: true
to the config section in thetesting/infra/k8s/base/stack/kibana.yaml
file. (This mimics the serverless config https://github.com/elastic/kibana/pull/154460/files#diff-ebeb9e9dc4c3ee5e81f743f0eda3c06f1fc161a11127b374d21f0da5e6368fd9R2)Run
tilt up
again, navigate to Index Management, and observe the lifecycle is now usingdata_rentention
rather than the ILM policy.Now, modify the retention period in
apmpackage/apm/data_stream/service_summary_interval_metrics/lifecycle.1m.yml
to1m
, and when theapmpackage
is reinstalled, generate some load so that the datastream is created.Go to Dev Tool, and confirm the
data_retention
for the datastream is correctly set by running the following:Should see
Related issues