Kibana unable to locate packetbeat index

Hi,

I have uploaded the custom dashboard and visualization using the beats dashboard. But when i go to view my dashboard , kibana is unable to find the index.

Can anyone help me to triage the issue. I have verified the topbeat and packetbeat yml files and they are pointing to correct elasticsearch IP.

Regards
Niraj

Are you sure the index exists? If you go to the settings area, do you have the pattern defined as well.

Here is my indices stats

green open .marvel-2015.10.19 1 1 5614 0 22.6mb 11.3mb
green open packetbeat-2015.10.23 5 1 16319 0 10.8mb 5.3mb
green open packetbeat-2015.10.19 5 1 13914 0 10mb 5mb
green open packetbeat-2015.10.25 5 1 12025 0 17.6mb 8.9mb
green open .marvel-2015.10.22 1 1 8608 0 39.4mb 19.7mb
green open topbeat-2015.10.26 5 1 238039 0 173.1mb 90.2mb
green open packetbeat-2015.10.24 5 1 7804 0 5.8mb 2.8mb
green open .marvel-2015.10.24 1 1 8599 0 38.4mb 19.2mb
green open twitter 5 1 0 0 1.2kb 720b
green open .marvel-2015.10.20 1 1 8619 0 38.9mb 19.4mb
green open .packetbeat-topology 5 1 1 0 13.2kb 6.7kb
green open .marvel-2015.10.23 1 1 8605 0 40.2mb 20.1mb
green open packetbeat-2015.10.18 5 1 1782 0 2mb 1mb
green open .marvel-2015.10.26 1 1 2488 0 23.5mb 11.7mb
green open packetbeat-2015.10.22 5 1 17682 0 11.5mb 5.7mb
green open packetbeat-2015.10.21 5 1 13638 0 9.1mb 4.6mb
green open .marvel-2015.10.25 1 1 8596 0 39.4mb 19.7mb
green open .kibana 1 1 93 0 211.3kb 74.3kb
green open packetbeat-2015.10.20 5 1 5739 0 4.5mb 2.2mb
green open .marvel-2015.10.21 1 1 8615 0 40.5mb 20.2mb

Right, but did you add the pattern in KB as well?

Yes i did. I believe this is what you meant. I am sorry if you suggested something else.

Except the pattern in the viz's is [packetbeat-]YYYY.MM.dd, not packetbeat-*.

I mean what difference does both make,it is just a regex to add all packetbeat. Or am i taking it wrong. How do i fix it would be my question rather.

Thanks for the hint. I finally fixed it.

I'm getting the same error.

How did you fix this issue?

I solved this issue updating the Dashboard templates. I downloaded the package "beats-dashboards-1.0.0" and than I executed the ./load.sh. Now the dashboard is working fine.
The link was very useful: https://www.elastic.co/guide/en/beats/libbeat/current/getting-started.html