Deprecation logs for APM Server (+Agents?)
Elastic Stack products will start to collect deprecation logs in an elasticsearch index. This issue tracks investigation of:
- collection of deprecation logs from APM Server itself
- utility of collecting deprecation logs from agents, likely via some new mechanism
- When will we deprecate RUM v2 protocol, given we now have v3? Need to check with the RUM agent devs on timeline.
- Will we deprecate secret token auth once API Key auth is GA?
- Once data streams and Fleet integration are done, deprecate template/pipeline/ILM etc. setup?
ES is going to write to .logs-deprecation-elasticsearch - let's consider writing to .logs-deprecation-apm to be aligned.
Any issues you can link to? Will Elasticsearch install a data stream index template for .logs-deprecation-*, or will we need to create our own?
Nothing to link to yet; good question around the data stream index template - this still needs to be figured out.
As of 7.13.0, Elasticsearch will install an index template matching .logs-deprecation-*: https://github.com/elastic/elasticsearch/pull/68737
I propose that we introduce config to enable deprecation logging, and have it enabled automatically when the output is Elasticsearch v7.13.0+. Our deprecation logs would go to .logs-deprecation.apm-default.
@simitt Are you planning to do that for 8.x? I've been looking at this from our side elastic/elastic-agent#122
We have not enabled it for 7.x, no concrete plans yet for 8.x.