Dashboard could not locate the index-pattern
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
Typically Packetbeat sets up the index pattern automatically when it loads the index template. However, if for some reason Packetbeat loads the index template, but the index pattern does not get created correctly, you’ll see a "could not locate that index-pattern" error. To resolve this problem:
Try running the
setupcommand again. For example:./packetbeat setup.If that doesn’t work, go to the Management app in Kibana, and under Index Patterns, look for the pattern.
If the pattern doesn’t exist, create it manually.
- Set the Time filter field name to
@timestamp. - Set the Custom index pattern ID advanced option. For example, if your custom index name is
packetbeat-customname, set the custom index pattern ID topacketbeat-customname-*.
- Set the Time filter field name to
For more information, see Creating an index pattern in the Kibana docs.