| .. | ||
| _meta | ||
| beater | ||
| cmd | ||
| config | ||
| decoder | ||
| docs | ||
| flows | ||
| include | ||
| lib/windows-64 | ||
| processor/add_kubernetes_metadata | ||
| procs | ||
| protocols | ||
| protos | ||
| publish | ||
| scripts | ||
| sniffer | ||
| tests | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| dashboards.yml | ||
| magefile.go | ||
| main.go | ||
| main_test.go | ||
| make.bat | ||
| Makefile | ||
| packetbeat.reference.yml | ||
| packetbeat.yml | ||
| README.md | ||
| SUPPORT_PROTOCOL.md | ||
Packetbeat
Packetbeat is an open source network packet analyzer that ships the data to Elasticsearch. Think of it like a distributed real-time Wireshark with a lot more analytics features.
The Packetbeat shippers sniff the traffic between your application processes, parse on the fly protocols like HTTP, MySQL, PostgreSQL, Redis or Thrift and correlate the messages into transactions.
For each transaction, the shipper inserts a JSON document into Elasticsearch, where it is stored and indexed. You can then use Kibana to view key metrics and do ad-hoc queries against the data.
To learn more about Packetbeat, check out https://www.elastic.co/products/beats/packetbeat.
Getting started
Please follow the getting started guide from the docs.
Documentation
Please visit elastic.co for the documentation.
Bugs and feature requests
If you have an issue, please start by opening a topic on the forums. We'll help you troubleshoot and work with you on a solution.
If you are sure you found a bug or have a feature request, open an issue on Github.
Contributions
We love contributions from our community! Please read the CONTRIBUTING.md file.
Snapshots
For testing purposes, we generate snapshot builds that you can find here. Please be aware that these are built on top of master and are not meant for production.