# zipkin を Homebrew, Nix でインストール zipkin のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。 ## インストール ```sh sudo av install brew:zipkin ``` 追加のインストールコマンド: ### macOS - Homebrew (100%): ```sh brew install zipkin ``` 証拠: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#zipkin ``` 証拠: nixpkgs package indexes: pkgs/by-name/zi/zipkin/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## パッケージ情報 - **パッケージキー:** brew:zipkin - **パッケージマネージャ:** Homebrew - **バージョン:** 3.6.1 - **ソース概要:** Collect and visualize traces written in Zipkin format - **ホームページ:** - **生成日時:** 2026-08-03T19:37:03+00:00 ## 実行可能ファイル - zipkin (エイリアス) ## インストール挙動 - Bottle: 利用不可 ## バージョンと鮮度 - ページ生成日: 2026-08-03 - マネージャ版: 3.6.1 ## プロジェクトの歴史と使われ方 Zipkin is a distributed tracing system born inside Twitter and later stewarded by the OpenZipkin volunteer organization. For package users it is the classic lightweight trace collector and UI: run a server, point instrumented services at it, and inspect latency paths through a service graph. ### プロジェクトの歴史 Twitter announced Zipkin as open source on 7 June 2012, describing it as a system created to gather timing data for requests moving through the services behind the Twitter API. The announcement says Zipkin began during Twitter's first Hack Week as a basic implementation of the Google Dapper paper for Thrift, then grew to support tracing HTTP, Thrift, Memcache, SQL, and Redis requests. OpenZipkin later became the project home. The official community page says Zipkin was originally created by Twitter and is now run by the OpenZipkin volunteer organization, which stewards code, docs, specs, and support. The server evolved into a standalone Java service with collectors, storage options, a query/UI layer, and instrumentation integrations. The current README and site describe support for HTTP or Kafka reporting, alternatives such as ActiveMQ, gRPC, RabbitMQ, and Pulsar, and storage backends including in-memory, Cassandra, and Elasticsearch. ### 採用の歴史 Zipkin's initial adoption came from Twitter's own production need to understand latency in a service-oriented architecture. The 2012 announcement says it helped find optimizations such as removing memcache requests, rewriting slow MySQL SELECTs, and fixing service timeouts. After open sourcing, Zipkin became one of the default names in distributed tracing alongside systems such as Dapper-inspired internal tools and later Jaeger. Its adoption was helped by a simple local demo path, a web UI, many instrumentation libraries, and a data model that other systems could emit. The OpenZipkin community page describes a volunteer-run project with GitHub repositories, a website, mailing list, chat, support channels, and community events. That community model is part of why Zipkin remained packageable after its Twitter-origin architecture changed hands. ### 使われ方 A typical user runs the Zipkin server, instruments applications with a tracer or instrumentation library, sends spans to Zipkin, and queries traces by service, operation, tags, duration, or trace ID. The UI shows trace waterfalls and a dependency diagram for aggregate service relationships. For local or package-manager use, the README documents running the server as a jar, Docker container, or installed command, then opening the UI on the Zipkin endpoint. In production, users choose collectors and storage backends according to the traffic and retention requirements of their service architecture. ### パッケージ好きにとっての重要性 Zipkin is important in package catalogs because it makes distributed tracing something a developer can install and run locally, not only a hosted observability product. That has made it useful for demos, integration tests, platform teams, and service owners validating instrumentation. It also occupies a historical bridge between the Dapper paper era and the broader observability ecosystem. The package is a runnable artifact of how tracing moved from large-company infrastructure into everyday open-source service stacks. ### タイムライン - 2012: Twitter open sources Zipkin after its Hack Week origin and production use. - 2013: Twitter publishes a browser-extension workflow showing continued work to make traces easier to consume. - 2010s: OpenZipkin becomes the volunteer organization stewarding Zipkin code, docs, specs, and support. - 2020s: Zipkin continues as a standalone server with multiple transports, storage backends, UI, and instrumentation integrations. ### Related projects - Google Dapper, the tracing paper that inspired Zipkin's original design. - Twitter Finagle, Scrooge, Scribe, Cassandra, ZooKeeper, Bootstrap, and D3, named by Twitter as early Zipkin dependencies or surrounding infrastructure. - Jaeger, OpenTelemetry, Brave instrumentation, service meshes, and other distributed tracing systems that interoperate with or sit near Zipkin in observability stacks. ### ソース - - - - - ## セキュリティノート formula declares a Homebrew service. - **Geiger リスク:** orange / 中 - formula declares a Homebrew service ## 他のパッケージマネージャ記録 - Nix - zipkin: normalized package name match | nixpkgs package indexes: pkgs/by-name/zi/zipkin/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/zipkin.yml](https://github.com/mxcl/pkgdb/blob/main/combined/zipkin.yml) ## ソース - 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