apmpackage: define DLM retention periods in apm package

[kyungeunni]

Motivation/summary

Define DLM retention periods corresponding to the default ILM policy's policy.delete.min_age to support DLM when configured.

Checklist

• Update CHANGELOG.asciidoc
• Update package changelog.yml (only if changes to apmpackage have been made)
  - [ ] Documentation has been updated

For functional changes, consider:

• Is it observable through the addition of either logging or metrics?
• Is its use being published in telemetry to enable product improvement?
• Have system tests been added to avoid regression?

How to test these changes

1. Run tilt up

2. Open Kibana, go to Index Management > Index Template, and choose one of the templates APM server manages, for example: metrics-apm.service_summary.1m

3. Check the lifecycle is pointing to the ILM policy
   

4. Run tilt down, add xpack.fleet.internal.disableILMPolicies: true to the config section in the testing/infra/k8s/base/stack/kibana.yaml file. (This mimics the serverless config https://github.com/elastic/kibana/pull/154460/files#diff-ebeb9e9dc4c3ee5e81f743f0eda3c06f1fc161a11127b374d21f0da5e6368fd9R2)

5. Run tilt up again, navigate to Index Management, and observe the lifecycle is now using data_rentention rather than the ILM policy.
   

6. Now, modify the retention period in apmpackage/apm/data_stream/service_summary_interval_metrics/lifecycle.1m.yml to 1m, and when the apmpackage is reinstalled, generate some load so that the datastream is created.

7. Go to Dev Tool, and confirm the data_retention for the datastream is correctly set by running the following:

GET _data_stream/metrics-apm.service_summary.1m-default/_lifecycle

Should see

{
  "data_streams": [
    {
      "name": "metrics-apm.service_summary.1m-default",
      "lifecycle": {
        "enabled": true,
        "data_retention": "1m"
      }
    }
  ]
}

8. See the documents are all deleted after a while (it's not precisely 1 minute to get deleted, so you might need to wait a bit longer than the data_retention period)

Related issues

• [Fleet] Support DLM from package-spec kibana#161905
• Add settings for data retention (DLM) package-spec#556

[mergify]

This pull request does not have a backport label. Could you fix it @kyungeunni? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-7.17 is the label to automatically backport to the 7.17 branch.
• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.

NOTE: backport-skip has been added to this pull request.

[mergify]

This pull request is now in conflicts. Could you fix it @kyungeunni? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b add-dlm upstream/add-dlm
git merge upstream/main
git push upstream add-dlm

[axw]

Assigning to myself for testing

[axw]

Looks good in serverless project. Here's a jq oneliner that works with the output of GET /_component_template:

jq -S '.[] | map(select(.name | endswith("@package"))) | map({(.name): .component_template.template.lifecycle.data_retention}) | add' component_templates.json 
{
  "logs-apm.app@package": "10d",
  "logs-apm.error@package": "10d",
  "metrics-apm.app@package": "90d",
  "metrics-apm.internal@package": "90d",
  "metrics-apm.service_destination.10m@package": "180d",
  "metrics-apm.service_destination.1m@package": "90d",
  "metrics-apm.service_destination.60m@package": "390d",
  "metrics-apm.service_summary.10m@package": "180d",
  "metrics-apm.service_summary.1m@package": "90d",
  "metrics-apm.service_summary.60m@package": "390d",
  "metrics-apm.service_transaction.10m@package": "180d",
  "metrics-apm.service_transaction.1m@package": "90d",
  "metrics-apm.service_transaction.60m@package": "390d",
  "metrics-apm.transaction.10m@package": "180d",
  "metrics-apm.transaction.1m@package": "90d",
  "metrics-apm.transaction.60m@package": "390d",
  "traces-apm.rum@package": "90d",
  "traces-apm.sampled@package": "1h",
  "traces-apm@package": "10d"
}

ILM policies continue to be installed in stateful.