Kibana version: 7.9.1
Elasticsearch version: 7.9.1
APM Server version: 7.9.1
Fresh install or upgraded from other version?: Upgraded from 7.9.0
Is there anything special in your setup? No
Description of the problem:
I'd like to create different indices per application for apm (cloud hosted). I've been told to update the settings in the cloud console or the api.
I'd love to use this setup:
setup.template.name: 'apm'
setup.template.pattern: 'apm-*'
apm-server.ilm.setup.enabled: false
setup.template.settings.index.number_of_replicas: 0
output.elasticsearch:
index: 'apm-%{[observer.version]}-%{+yyyy-MM}'
indices:
- index: 'apm-%{[observer.version]}-%{[kubernetes.labels.department]}-%[kubernetes.labels.app]}-%{+yyyy-MM}'
when:
not:
or:
- equals:
kubernetes.namespace: botkube
- equals:
kubernetes.namespace: cert-manager
- equals:
kubernetes.namespace: default
- equals:
kubernetes.namespace: kube-node-lease
- equals:
kubernetes.namespace: kube-public
- equals:
kubernetes.namespace: kube-system
Within the UI of the cloud console this seems to work but upon trying to save i'm getting:
Within heartbeat, filebeat and metricbeat we use this same configuration and that seems to do the job very well as we get different indices per application.
What i'd like to achieve is to show the correct apm-info per space within kibana so that the application specific space only has that specific apm data instead of all the apm data available.
This seems to work just fine for heartbeat, metricbeat and filebeat.