we are capturing enterprise java traces, and the trace is filling up all the spaces on my cluster, its generating 1.4TB daily and i cant keep up, then upon checking there is no compression on the created index and its just a standard index, is there any reason this was used as default and if i can change the template to timeseries or logsdb ?
Kibana version: 9.2
Elasticsearch version: 9.2
APM Server version: elastic-agent 9.2
APM Agent language and version: java 1.54
Great question / common question
In short work work was stopped on making sure that logs DB which would be the mode used was fully tested and supported for legacy APM agents because focus is on OTEL.
My understanding is there's a few places in the curated UI that will not work properly if you convert your traces to logs DB... You can certainly try it but it would not be supported if you had issues.
Out of the box OTEL traces are logsdb.
© 2020. All Rights Reserved - Elasticsearch
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.