As per the current APM Index Strategy proposal, we need the ability to use service.name as a data stream name, or part of a data stream name.
service.name is a top level indexed field in APM documents (example, spec), and having it in the data_stream would give us the guarantee that each APM service will have its own indices. This would improve performance, allow users to have more granular security and retention policies, and simplify the APM experience in general.
So for metrics data, for instance, we would have indices looking like:
metrics-backend_service-production
metrics-backend_service.profiles-production
metrics-frontend_service-staging
Same thing for other types (traces, logs).
Right now, I believe folders in the package need to match exactly the data stream name set in manifest.yml, so we would need to circumvent that limitation as well.
As per the current APM Index Strategy proposal, we need the ability to use
service.nameas a data stream name, or part of a data stream name.service.nameis a top level indexed field in APM documents (example, spec), and having it in thedata_streamwould give us the guarantee that each APM service will have its own indices. This would improve performance, allow users to have more granular security and retention policies, and simplify the APM experience in general.So for metrics data, for instance, we would have indices looking like:
metrics-backend_service-productionmetrics-backend_service.profiles-productionmetrics-frontend_service-stagingSame thing for other types (traces, logs).
Right now, I believe folders in the package need to match exactly the data stream name set in
manifest.yml, so we would need to circumvent that limitation as well.