### Author:  [@alerta](https://discuss.elastic.co/u/alerta)
#### Post date: [March 6, 2019, 7:40am UTC](https://discuss.elastic.co/t/theres-no-apm-index-pattern-available-to-use-the-query-bar-6-5-4/171040/1 "2019-03-06T07:40:27Z")
**Kibana version** : 6.5.4
**Elasticsearch version** : 6.5.4
**APM Server version** : 6.5.4
**APM Agent language and version** : java 1.4.0
**Browser version** : Version 69.0.3497.100 (Official Build) (64-bit)
**Original install method (e.g. download page, yum, deb, from source, etc.) and version**: docker
**Fresh install or upgraded from other version?** upgrade from 6.3
**Is there anything special in your setup?** For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc.
Nope, use elasticsearch output
**Description of the problem including expected versus actual behavior. Please include screenshots (if relevant)**:
apm-server.yml
setup.kibana.host: "kibana-host"
setup.dashboards.enabled: true
setup.dashboards.index: "apm\*"
setup.dashboards.retry.enabled: true
max\_procs: 4
queue.mem.events: 4096
apm-server.host: 0.0.0.0:8200
apm-server.concurrent\_requests: 5
apm-server.rum.enabled: true
apm\_oss.indexPattern: apm\*
apm\_oss.errorIndices: apm\*
apm\_oss.spanIndices: apm\*
apm\_oss.transactionIndices: apm\*
apm\_oss.onboardingIndices: apm\*
output.elasticsearch:
hosts: "elasticsearch-host"
indices:
- 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"
---
### Author:  [@Felix\_Roessel](https://discuss.elastic.co/u/Felix_Roessel)
#### Post date: [March 6, 2019, 1:58pm UTC](https://discuss.elastic.co/t/theres-no-apm-index-pattern-available-to-use-the-query-bar-6-5-4/171040/2 "2019-03-06T13:58:06Z")
Did you tried to click on this button in Kibana at \/app/kibana#/home/tutorial/apm
---
### Author:  [@alerta](https://discuss.elastic.co/u/alerta)
#### Post date: [March 6, 2019, 3:10pm UTC](https://discuss.elastic.co/t/theres-no-apm-index-pattern-available-to-use-the-query-bar-6-5-4/171040/3 "2019-03-06T15:10:38Z")
I tried this many times. But it's still not working
---
### Author:  [@digitalron](https://discuss.elastic.co/u/digitalron)
#### Post date: [March 6, 2019, 3:51pm UTC](https://discuss.elastic.co/t/theres-no-apm-index-pattern-available-to-use-the-query-bar-6-5-4/171040/4 "2019-03-06T15:51:33Z")
Have you tried to go to the Kibana management page, select Kibana index patterns, and click "create index pattern" there?
---
### Author:  [@alerta](https://discuss.elastic.co/u/alerta)
#### Post date: [March 6, 2019, 3:52pm UTC](https://discuss.elastic.co/t/theres-no-apm-index-pattern-available-to-use-the-query-bar-6-5-4/171040/5 "2019-03-06T15:52:50Z")
Index pattern created automatically after start apm-server
---
### Author:  [@digitalron](https://discuss.elastic.co/u/digitalron)
#### Post date: [March 6, 2019, 4:13pm UTC](https://discuss.elastic.co/t/theres-no-apm-index-pattern-available-to-use-the-query-bar-6-5-4/171040/6 "2019-03-06T16:13:38Z")
Have you tried accessing the index from the console, like do a query against it? In the Index management page, do you see the index properly set up? Try also refreshing the index via the management page
---
### Author:  [@alerta](https://discuss.elastic.co/u/alerta)
#### Post date: [March 7, 2019, 6:01am UTC](https://discuss.elastic.co/t/theres-no-apm-index-pattern-available-to-use-the-query-bar-6-5-4/171040/7 "2019-03-07T06:01:40Z")
Yep.
---
### Author:  [@sqren](https://discuss.elastic.co/u/sqren)
#### Post date: [March 8, 2019, 3:20pm UTC](https://discuss.elastic.co/t/theres-no-apm-index-pattern-available-to-use-the-query-bar-6-5-4/171040/8 "2019-03-08T15:20:33Z")
Hi Eugeny,
This might be caused by a bug affecting 6.5 where the APM index pattern sometimes cannot be found if you have more than ~20 index patterns.
This has been fixed in 6.6: [https://github.com/elastic/kibana/pull/26245](https://github.com/elastic/kibana/pull/26245)
Can you please see how many index patterns you have listed in the Mangement section?
Thanks!
---
### Author:  [@alerta](https://discuss.elastic.co/u/alerta)
#### Post date: [March 11, 2019, 12:21pm UTC](https://discuss.elastic.co/t/theres-no-apm-index-pattern-available-to-use-the-query-bar-6-5-4/171040/9 "2019-03-11T12:21:52Z")
Yes, you are right, we have more than 20 index patterns. After upgrade to 6.6.1 problem has disappeared
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 1, 2019, 8:27am UTC](https://discuss.elastic.co/t/theres-no-apm-index-pattern-available-to-use-the-query-bar-6-5-4/171040/10 "2019-04-01T08:27:42Z")
This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.