The indices are not writing to the default names.
It looks like perhaps the apm-server.yml has been edited in the output.elasticsearch section and is no longer using the defaults particularly with respect to the indices names, did you make other changes?
If you wanted to use the default behavior you should not have edited that section.
I would go back to the original / default apm-server.yml. Make the minimal changes for the connections and restart the apm server and see if you get the correct indices.
I am not sure how to / if fix the old data, lets try to get it working first
Should look like....
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open apm-7.11.1-transaction-000001 uxazSOaySeSbyUu1XU_mhQ 1 1 7531683 0 5.3gb 2.6gb
green open apm-7.11.1-span-000001 WG9zlj0JQ6yvYAKKJ6Owgg 1 1 28420552 0 12gb 6gb
green open apm-7.11.1-profile-000001 U2NgU2fVRUeiQkk6jKd9gg 1 1 0 0 416b 208b
green open apm-7.11.1-metric-000001 mP6PcMBCSFeehkHj4NaaTQ 1 1 1868972 0 479mb 239.7mb
green open apm-7.11.1-error-000001 R0Xx_1HMRzq4X4wpsUeeBA 1 1 48251 0 117.7mb 58.7mb
Default yml
output.elasticsearch:
# Array of hosts to connect to.
# Scheme and port can be left out and will be set to the default (`http` and `9200`).
# In case you specify and additional path, the scheme is required: `http://localhost:9200/path`.
# IPv6 addresses should always be defined as: `https://[2001:db8::1]:9200`.
hosts: ["localhost:9200"]
...
# By using the configuration below, APM documents are stored to separate indices,
# depending on their `processor.event`:
# - error
# - transaction
# - span
# - sourcemap
#
# The indices are all prefixed with `apm-%{[observer.version]}`.
# To allow managing indices based on their age, all indices (except for sourcemaps)
# end with the information of the day they got indexed.
# e.g. "apm-7.3.0-transaction-2019.07.20"
#
# Be aware that you can only specify one Elasticsearch template.
# If you modify the index patterns you must also update these configurations accordingly,
# as they need to be aligned:
# * `setup.template.name`
# * `setup.template.pattern`
#index: "apm-%{[observer.version]}-%{+yyyy.MM.dd}"
#indices:
# - index: "apm-%{[observer.version]}-sourcemap"
# when.contains:
# processor.event: "sourcemap"
#
# - index: "apm-%{[observer.version]}-error-%{+yyyy.MM.dd}"
# when.contains:
# processor.event: "error"
#
# - index: "apm-%{[observer.version]}-transaction-%{+yyyy.MM.dd}"
# when.contains:
# processor.event: "transaction"
#
# - index: "apm-%{[observer.version]}-span-%{+yyyy.MM.dd}"
# when.contains:
# processor.event: "span"
#
# - index: "apm-%{[observer.version]}-metric-%{+yyyy.MM.dd}"
# when.contains:
# processor.event: "metric"
#
# - index: "apm-%{[observer.version]}-onboarding-%{+yyyy.MM.dd}"
# when.contains:
# processor.event: "onboarding"
# A pipeline is a definition of processors applied to documents when ingesting them to Elasticsearch.
# APM Server comes with a default pipeline definition, located at `ingest/pipeline/definition.json`, which is
# loaded to Elasticsearch by default (see `apm-server.register.ingest.pipeline`).
# APM pipeline is enabled by default. To disable it, set `pipeline: _none`.
#pipeline: "apm"
...
Also I would clear this out back to the defaults / empty.
