IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Monitoring UI shows fewer Beats than expected High RSS memory usage due to MADV settings »
Elastic Docs ›Packetbeat Reference [8.15] ›Troubleshoot ›Common problems

Dashboard could not locate the index-pattern

edit

Dashboard could not locate the index-pattern

edit

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:

  1. Try running the setup command again. For example: ./packetbeat setup.

  2. If that doesn’t work, go to the Management app in Kibana, and under Index Patterns, look for the pattern.

    1. 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 to packetbeat-customname-*.

For more information, see Creating an index pattern in the Kibana docs.

« Monitoring UI shows fewer Beats than expected High RSS memory usage due to MADV settings »