From efc3c61ee9a6f9cdd2bacf1e697915934ecb1d5f Mon Sep 17 00:00:00 2001 From: Tudor Golubenco Date: Sun, 13 Sep 2015 19:35:40 +0900 Subject: [PATCH] Removed outdated information from the README file I removed what was updated, like the link to packetbeat.com. I also removed the list of dashbaords because that will always be hard to maintain the repository. I didn't update the screenshots with the PR. In general, I think having no screenshots is worse than having slightly out of date screenshots, so I'm not too worried about that part lagging behind occasionally. --- README.md | 14 ++------------ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/README.md b/README.md index 00ffbab7c0b..ce23d5b1133 100644 --- a/README.md +++ b/README.md @@ -1,12 +1,8 @@ Packetbeat dashboards ===================== -This repository contains sample Kibana4 dashboards for application and network -tracing and performance monitoring. They are meant to be used together with the -Packetbeat agents and Elasticsearch. - -See http://packetbeat.com for details. - +This repository contains sample Kibana4 dashboards for visualizing the data +gathered by the Elastic [Beats](https://www.elastic.co/products/beats). Installation ------------- @@ -16,12 +12,6 @@ URL: ./load.sh http://localhost:9200 -You should now have the following pages loaded in Kibana: - - - **Packetbeat Statistics**: Contains high-level views like the network topology, the application layer protocols repartition, the response times repartition, and others. - - **Packetbeat Search**: This page enables you to do full text searches over the indexed network messages. - - **MySQL Performance**: This page demonstrates more advanced statistics like the top N slow MySQL queries, most frequent MySQL queries, the database throughput or database responsetime. To investigate a failure in your network, you can drill down to see all MySQL transactions in real-time. - - **PgSQL Performance**: Similar with MySQL Performance dashboard, but for the Postgresql transactions. If you want to use HTTP authentication for Elasticsearch, you can specify the credentials as a second parameter: