Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use [packetbeat-]YYYY.MM.DD #186

Merged
merged 1 commit into from
Sep 4, 2015
Merged

Use [packetbeat-]YYYY.MM.DD #186

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/gettingstarted.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -307,12 +307,12 @@ Now point your browser to port 5601 and you should see the Kibana web
interface.

The first thing you need to do is to configure the index pattern. In
the *Index name or pattern* field enter `packetbeat-*` and for the *Time-field
the *Index name or pattern* field enter `[packetbeat-]YYYY.MM.DD` and for the *Time-field
name* select `timestamp`.

image:./images/kibana-index-pattern.png[Kibana index pattern]

If after you configure the `packetbeat-*` index pattern Kibana still says
If after you configure the `[packetbeat-]YYYY.MM.DD` index pattern Kibana still says
_Unable to fetch mapping. Do you have indices matching the pattern?_, it means
that Packetbeat hasn't yet written any data into Elasticsearch. Make sure that
some traffic was running on your servers and that Packetbeat could see it.
Expand Down