Installer packetbeat avec Homebrew, chocolatey, Nix

Liens du projet

• Page d'accueil
• Dépôt
• Page du gestionnaire de paquets

Commandes et alias

• packetbeat

Historique du projet

Monica Sarbu and Tudor Golubenco created Packetbeat after working in network packet analytics and encountering the complexity of extracting useful application information from wire data. The project correlated requests and responses from captured application protocols and emitted structured events for Elasticsearch.

Elastic acquired Packetbeat on May 27, 2015. Packetbeat then became the foundation for the Beats framework, a shared Go-based platform for small operational-data shippers.

Beats 1.0.0 was released on November 24, 2015 with Packetbeat, Filebeat, and Topbeat as the first officially supported Beats. Packetbeat has since been maintained in Elastic's shared Beats repository.

Historique d'adoption

Elastic acquired Packetbeat in May 2015 and used it as the starting point for the broader Beats family of lightweight data shippers. Packetbeat became one of the first officially supported Beats when the production-ready Beats platform was announced in November 2015.

Packetbeat is deployed on application hosts, containers, dedicated monitoring servers, switch mirror ports, and network taps. Its integration with Elasticsearch, Logstash, and Kibana made application-layer network observations part of the same operational-data workflow as logs and metrics.

Modes d'utilisation

Operators configure capture interfaces and protocols in packetbeat.yml, then run Packetbeat on application hosts or against mirrored or tapped traffic. It extracts fields such as latency, status, addresses, and protocol-specific transaction data.

Packetbeat can publish directly to Elasticsearch or through Logstash. Elastic provides setup commands for index templates and Kibana dashboards, while sensitive configuration values can be placed in the Packetbeat keystore under path.data.

Pourquoi les passionnés de paquets s'y intéressent

Packetbeat helped establish the lightweight-agent pattern in the Elastic ecosystem: capture data close to its source, normalize it into structured events, and ship it to a central analysis system.

For package maintainers and operators it combines several traditionally separate concerns—privileged packet capture, protocol decoding, service configuration, secret storage, and observability-stack integration—in one deployable agent.

Chronologie

• 2015-05-27: Elastic acquires Packetbeat and announces the Beats framework.
• 2015-11-24: Beats 1.0.0 makes Packetbeat one of the first officially supported Beats.

Related projects

• Packetbeat is built on the libbeat framework and maintained in the Elastic Beats monorepo.
• Elasticsearch stores and searches Packetbeat events, Logstash can process them in transit, and Kibana provides visualization and analysis.
• Other official Beats apply the same shipper model to logs, metrics, availability, audit data, and Windows events.

Sources

• https://www.elastic.co/blog/beats-1-0-0
• https://www.elastic.co/cn/about/press/elastic-acquires-packetbeat
• https://www.elastic.co/docs/reference/beats
• https://www.elastic.co/docs/reference/beats/packetbeat