Installer alp avec Homebrew, Nix

Liens du projet

• Page d'accueil
• Docs amont
• Page du gestionnaire de paquets

Commandes et alias

• alp

Historique du projet

The official README describes alp simply as Access Log Profiler and documents binary releases, Homebrew installation, asdf installation, and command-based usage. The repository's v0.4.0-to-v1.0.0 migration document records a major reshaping from an LTSV-focused profiler into a multi-format tool with subcommands.

Version 1.0.0 added format-specific subcommands such as `ltsv`, `json`, and `regexp`, later joined in the README by `pcap`, `diff`, and `count`. The v1 transition also consolidated sorting and output options, added filters, added selectable output columns, and introduced position-file support so repeated benchmark runs do not require truncating logs.

Historique d'adoption

alp is a focused operations tool rather than a broad observability platform. Its adoption comes from developers and performance testers who want a quick CLI profile of HTTP access logs, especially during load testing or application tuning.

Official installation paths include GitHub release binaries, Homebrew on macOS, and asdf through `asdf-alp`. That makes it easy to pin a profiler version in local benchmark environments without introducing a full logging stack.

Modes d'utilisation

Common usage is to feed alp an access log in LTSV, JSON, or regexp-parsed format and sort/group the results by count, latency statistics, status, URI, method, percentiles, or matching groups. It can output table, markdown, TSV, CSV, and HTML formats.

The README also documents `pcap` profiling for captured HTTP requests, `diff` for comparing two profile results, and `count` for counting log entries. Many flags are label/key/subexpression overrides, which lets alp adapt to site-specific log formats without a separate parser.

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

alp is the sort of small Go CLI that package managers are good at: one binary, clear terminal behavior, and direct value in incident or benchmark loops. It sits between ad hoc `awk` pipelines and heavier log-analysis systems.

The v0.4-to-v1 migration is useful package history because it changed the command surface. Anyone packaging shell completions, examples, or old benchmark scripts needs to know that the older one-command LTSV shape became a subcommand-based multi-format CLI.

Chronologie

• v0.4.0: Documented as an Access Log Profiler for LTSV.
• v1.0.0: Added subcommands and support for JSON and regexp formats, with consolidated options and filters.
• Current: README documents LTSV, JSON, regexp, pcap, diff, count, Homebrew, asdf, and binary release installation.

Related projects

• LTSV is one of alp's first-class log formats.
• asdf-alp provides asdf-based version management for alp.
• Go libraries in the module include cobra, viper, go-ltsv, gopacket, and YAML packages.

Sources

• https://raw.githubusercontent.com/tkuchiki/alp/master/README.md
• https://raw.githubusercontent.com/tkuchiki/alp/master/docs/the_difference_between_v0_4_0_and_v1_0_0.md
• https://raw.githubusercontent.com/tkuchiki/alp/master/go.mod