Document specific steps for using custom index pattern with provided dashboards

[adoerrES]

• Version: 7.0 / 7.1
• Operating System: Mac or Windows 10
• Discuss Forum URL:
• Steps to Reproduce:

If a user wants to use the beats-provided Kibana dashboards but use a custom index-pattern name, the steps to get this to work out of the box could be better documented.

The following meta-issue exists to make using custom index-patterns with the dashboards more user friendly, so this issue can fall beneath that:
#3691

For example, if a user is using Filebeat 7.0 and wants to load the example dashboards but with an index pattern different than filebeat-*, we found the following steps (at least) are necessary however they are not documented (these may not be exhaustive or conclusive, just an example from preliminary testing):

• we needed to add the custom index pattern ID in the hidden (by default) Advanced Options setting in Kibana, on the Index Pattern screen.

• it wasn't clear if when using Filebeat modules like the IIS module, if users are expected to modify the index pattern name in the module file like filebeat-7.1.0-darwin-x86_64/kibana/7/dashboard/Filebeat-iis.json, but an index pattern value does exist in this file.

• The only mention we really have of custom index patterns with these dashboards is for the setup.dashboards.index setting description, so not sure if any missing steps should be added here, or if an actual step by step section for using the custom pattern should be written (since there may be multiple steps involved)?

[botelastic]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[botelastic]

This issue doesn't have a Team:<team> label.