# grok mit Homebrew, MacPorts installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für grok in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:grok ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install grok ``` Evidenz: local Homebrew formula metadata - MacPorts (94%): ```sh sudo port install grok ``` Evidenz: MacPorts ports tree: sysutils/grok/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ## Paketfakten - **Paketschlüssel:** brew:grok - **Paketmanager:** Homebrew - **Version:** 0.9.2 - **Quellzusammenfassung:** DRY and RAD for regular expressions and then some - **Homepage:** - **Repository:** - **Zuletzt aktualisiert:** 2026-08-02T20:52:08+09:00 - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - discogrok (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 0.9.2 ## Projektgeschichte und Nutzung Jordan Sissel's grok is a small Unix-oriented log parsing tool that turns reusable regular-expression patterns into structured output. ### Projektgeschichte The project predates its GitHub repository through the semicomplete.com and Google Code era referenced from the repository metadata. Its manual page describes the command as software for parsing logs, handling events, and turning unstructured text into structured data. The C implementation builds a `grok` command, `discogrok`, and a shared library. Its pattern-file model lets users name regular expressions once and compose them in match blocks instead of repeating long PCRE expressions across log-processing configurations. ### Adoptionsgeschichte The standalone package remained a niche command-line tool, but the grok pattern idea became culturally important in log processing. Similar pattern syntax appears in widely used log pipelines and observability products, while the original package stayed available through package managers such as Homebrew and MacPorts. ### Wie es verwendet wird A typical invocation points `grok` at a configuration file with `-f`. Configurations declare inputs such as files or command output, define match blocks, and emit reactions such as the original line, captured fields, JSON, or shell-command input. ### Warum Paket-Nerds sich dafür interessieren For package nerds, the appeal is the old-school Unix shape: a C command, PCRE-backed named patterns, installable pattern files, and log parsing without pulling in a larger log-ingestion stack. ### Zeitleiste - 2011: The GitHub repository was created and release tags from the 2011 series were published. - 2012: Homebrew and other package ecosystems carried the standalone tool during the early 2010s log-processing boom. - 2020s: The original project persisted as a niche packaged utility while grok-style patterns became common in larger logging systems. ### Related projects - Related projects include Jordan Sissel's Ruby grok implementation, Logstash-style grok filters, and observability tools that use named pattern matching for unstructured logs. - It is also adjacent to traditional text-processing tools such as grep, awk, sed, and PCRE-based command-line filters. ### Quellen - - - - ## Sicherheitshinweise narrow executable package without higher-risk signals. - **Geiger-Risiko:** grün / niedrig - narrow executable package without higher-risk signals ## Andere Paketmanager-Einträge - MacPorts - grok: normalized package name match | MacPorts ports tree: sysutils/grok/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/grok.yml](https://github.com/mxcl/pkgdb/blob/main/combined/grok.yml) ## Quellen - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph