Hey @Emirii, welcome to the group. Based on the screenshot of the available apm indices, it appears all APM data is directed to apm-%{[beat.version]}-%{+yyyy.MM.dd} index. I expect the following query will return the sourcemaps you have uploaded, can you confirm?
GET apm-*/_search
{
"query": {
"term": {
"processor.event": "sourcemap"
}
}
}
If so, dId you intend for that to be the case? The recommended index configuration in 6.8.1 for apm-server.yml is:
output.elasticsearch
- index: "apm-%{[beat.version]}-sourcemap"
when.contains:
processor.event: "sourcemap"
- index: "apm-%{[beat.version]}-error-%{+yyyy.MM.dd}"
when.contains:
processor.event: "error"
- index: "apm-%{[beat.version]}-transaction-%{+yyyy.MM.dd}"
when.contains:
processor.event: "transaction"
- index: "apm-%{[beat.version]}-span-%{+yyyy.MM.dd}"
when.contains:
processor.event: "span"
- index: "apm-%{[beat.version]}-metric-%{+yyyy.MM.dd}"
when.contains:
processor.event: "metric"
- index: "apm-%{[beat.version]}-onboarding-%{+yyyy.MM.dd}"
when.contains:
processor.event: "onboarding"
If it is intended, you should configure apm-server to look for sourcemaps in apm-*, replacing the default of apm-*-sourcemap. This can be done in apm-server.yml with apm-server.rum.source_mapping.index_pattern.