pkg.soopen package index

brew / Rang 6667

packetbeat mit Homebrew, chocolatey, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für packetbeat in AI-Agent-Workflows.

InstallationsbefehlSicherheitshinweise

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install packetbeat

local Homebrew formula metadata

Überblick

Paketzusammenfassung

Lightweight Shipper for Network Data

Befehle und Aliase

  • packetbeat

Verlauf

Projektgeschichte und Nutzung

Packetbeat is Elastic's lightweight real-time network packet analyzer and data shipper. It captures traffic, decodes supported application protocols, correlates requests with responses, and sends structured transactions to Elasticsearch or Logstash.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

  • 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.

Sicherheitslage

Risikostufe: orange

formula declares a Homebrew service.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • formula declares a Homebrew service

Signale

  • metadata:service

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Formelmetadaten deklarieren einen Service- oder Daemon-Block.
  • Homebrew-Bottle-Metadaten sind für 5 Plattformziele verfügbar.
  • Build-Metadaten listen 2 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Linux
/etc/packetbeat/packetbeat.yml
macOS
packetbeat.yml in the Packetbeat installation directory
Windows
C:\Program Files\Packetbeat\packetbeat.yml

Credential files

Credential-bearing paths to review before unattended agent runs.

Linux
Packetbeat keystore in the directory defined by path.data
macOS
Packetbeat keystore in the directory defined by path.data
Windows
Packetbeat keystore in the directory defined by path.data

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
packetbeatcliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-11-04
Manager-Version9.5.6
Manager aktualisiert2026-11-02
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://github.com/elastic/beats

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:packetbeat
Version9.5.6
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/packetbeat
Homepagehttps://www.elastic.co/products/beats/packetbeat
Repositoryhttps://github.com/elastic/beats
Upstream-Dokumentationhttps://www.elastic.co/products/beats/packetbeat
LizenzApache-2.0
Quellarchivhttps://github.com/elastic/beats.git
Zuletzt aktualisiert2026-11-02T16:50:57Z
Pulseupdated
Build-Abhängigkeitengo, mage
Von macOS bereitgestellte Bibliothekenlibpcap
Bottleverfügbar (auf arm64_golden_gate, arm64_linux, arm64_sequoia, arm64_tahoe, x86_64_linux)
Homebrew post-installnicht definiert
Dienstdeclared

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namepacketbeat
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

packetbeat

nix profile install nixpkgs#packetbeat
  • normalized package name match
  • Abgeglichen nach: Packetbeat
nixpkgs package indexes · raw.githubusercontent.com · nixpkgs package indexes: packetbeat from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix
Chocolatey95%

packetbeat

choco install packetbeat
  • normalized package name match
  • Abgeglichen nach: Packetbeat
Chocolatey community package catalog · community.chocolatey.org · Chocolatey community package catalog: packetbeat from https://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='11','origin'

Paketgraph

Links stammen aus dem lokalen Paketbeziehungsgraph, Ergänzungen, Abhängigkeitskanten, Ecosystem-Matches und Paket-Hub-Mitgliedschaft.

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment
  • pkg.so package database
  • pkgdb category and tag curation