-
Notifications
You must be signed in to change notification settings - Fork 70
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.
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
Sample Kibana dashboards #69
Comments
That is not really official, but you can find dashboard for beta 2 here : https://github.com/Ingensi/beats-dashboards/tree/dockerbeat I just update the repo with my current local version. Blkio visualizations are missing.. |
That's great! Thank you. |
Note, all occurences of |
Basically: # get it
git clone https://github.com/Ingensi/beats-dashboards.git
# go into folder
cd beats-dashboards/
# switch to right branch
git checkout dockerbeat
# or the exact commit:
#git checkout f7a1e93eb387e431fcdf810e49a081d4a84b585d
# replace dockerbeat with dockbeat
find . -type f -exec sed -i 's/dockerbeat/dockbeat/g' {} +
# load it into the server
./load.sh -url 'http://elastic:9200/' |
The docker module in metricbeat (which was contributed by dockbeat) contains also dashboards. |
@ruflin: so do I stilll need to make this process outlined in the second post? |
@luckydonald Not sure I can follow your question? |
@ruflin What do I have to to now, to get dashboards? |
Are you running dockbeat or metricbeat? |
Wait... There are now two to choose from? I skipped over the part with the Metricbeat Docker module, you were talking about, sorry. I currently have neither running, the last time I did, there were some memory issues (#139). |
Dockbeat was converted to a module for metricbeat and contributed. So they have the exact same foundation. Recently most changes/fixes went into the docker module in metricbeat. |
It would be very useful if you could provide some Kibana templates for dockerbeat.
Like Elastic does for topbeat: https://github.com/elastic/beats-dashboards
The text was updated successfully, but these errors were encountered: