Automic VaultAutomic Vault

brew

使用 Homebrew, Nix 安装 opentsdb

查看 opentsdb 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install opentsdb

local Homebrew formula metadata

Linux

Nix已验证 · 92%
nix profile install nixpkgs#opentsdb

nixpkgs package indexes · pkgs/by-name/op/opentsdb/package.nix · 来源: api.github.com

概览

软件包摘要

Scalable, distributed Time Series Database

命令和别名

  • start-tsdb.sh
  • tsdb

历史

项目历史与用法

OpenTSDB is a distributed time-series database built on HBase for storing, indexing, querying, and graphing high-volume metrics without downsampling away raw granularity. It ships a Time Series Daemon, command-line tools, HTTP and telnet-style APIs, and an HBase schema tuned for metric names, timestamps, and tags.

项目历史

OpenTSDB was originally designed and implemented at StumbleUpon by Benoît Sigoure, with early design input from Berk D. Demir. It grew out of the operational need to collect metrics from networks, operating systems, applications, and services at a scale where older fixed-size or single-node monitoring stores were not sufficient.

The project chose HBase because it could distribute writes and scans across a cluster while keeping raw metric points for long periods. Public talks and documentation from the early 2010s emphasized billion-point-per-day ingestion, large numbers of time series, and avoiding the loss of precision common in round-robin databases.

采用历史

OpenTSDB’s adoption followed the rise of large Hadoop/HBase installations and high-cardinality infrastructure monitoring. Its contributor list includes companies such as StumbleUpon, Yahoo, Box, Arista Networks, Betfair, Limelight Networks, and others, showing use beyond the original StumbleUpon deployment.

Its protocol and data model also outlived some deployments of the original server. Cloud vendors and monitoring tools documented OpenTSDB-compatible ingestion or comparison points because the metric-plus-tags model became a familiar shape for time-series telemetry systems.

使用方式

Operators run one or more independent TSD processes in front of HBase or Google Bigtable-compatible storage. Collectors such as tcollector, collectd, StatsD bridges, or custom scripts send datapoints, while users query and graph by metric, timestamp range, and tags through the HTTP API or built-in UI.

For package users, the interesting pieces are the `tsdb` command, `start-tsdb.sh`, the configuration search path, and the dependency on a correctly prepared HBase schema. Installing the package is only the first step; a usable OpenTSDB deployment depends on distributed storage, collectors, and retention choices.

为什么软件包爱好者会关心

OpenTSDB is a reminder that some packages are operational systems disguised as CLIs. The formula installs Java code and scripts, but the real dependency is an HBase-backed monitoring architecture with schema, collectors, ports, and dashboards.

时间线

  • 2010: OpenTSDB was written at StumbleUpon to handle large-scale service metrics.
  • 2012: public talks described StumbleUpon deployments adding over one billion datapoints per day.
  • 2014: OpenTSDB 2.0-era material described the project as a distributed, scalable time-series database with broader community involvement.
  • 2020s: OpenTSDB 2.4 documentation remained the main reference for the classic HBase-backed architecture.

Related projects

  • Related projects include HBase, Google Bigtable, tcollector, collectd, StatsD, Grafana, Prometheus, InfluxDB, Graphite, and cloud services that expose OpenTSDB-compatible APIs.

安全态势

风险级别:orange

broad file, network, media, or database tool signal. formula declares a Homebrew service.

风险分类器

orange 风险 · 中 置信度 · infrastructure

原因

  • broad file, network, media, or database tool signal
  • formula declares a Homebrew service

信号

  • metadata:service
  • text:database

安装行为

  • Homebrew 为此 formula 声明了 post-install 钩子。
  • formula 元数据声明了服务或守护进程块。
  • Homebrew bottle 元数据适用于 4 个平台目标。
  • 安装时包含 4 个运行时依赖。
  • 构建元数据列出 4 个构建依赖。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

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.

Unix
./opentsdb.conf/etc/opentsdb.conf/etc/opentsdb/opentsdb.conf/opt/opentsdb/opentsdb.conf

可执行文件

已安装的可执行文件

命令类型暴露范围备注
start-tsdb.shcli全局可执行文件
tsdbcli全局可执行文件

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-07-10
管理器版本2.4.1
管理器更新时间2026-06-22
本地数据OK
上游当前
检测到的最新版本v2.4.1

https://github.com/OpenTSDB/opentsdb

  • OK没有生成新鲜度警告。

安装元数据

软件包元数据

软件包键brew:opentsdb
版本2.4.1
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/opentsdb
主页http://opentsdb.net/
仓库https://github.com/OpenTSDB/opentsdb
上游文档https://opentsdb.net/docs/build/html/index.html
许可证LGPL-2.1-or-later
源码归档https://github.com/OpenTSDB/opentsdb/archive/refs/tags/v2.4.1.tar.gz
最后更新2026-06-22T14:05:45-07:00
Pulseupdated
依赖gnuplot, hbase, lzo, openjdk@11
构建依赖autoconf, automake, openjdk@8, python@3.13
Bottle可用 (于 arm64_linux, sonoma, ventura, x86_64_linux)
Homebrew post-install已定义
服务declared

注册表事实

源数据库详情

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameopentsdb
Version Scheme0
Revision0
Requirements
  • arch
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedyes
Disabledno
Keg Onlyno
URL Keys
  • stable

源数据库匹配

其他软件包管理器记录

匹配项来自外部软件包管理器索引,并与本地 Automic Vault 软件包链接分开显示。

Nix95%

opentsdb

nix profile install nixpkgs#opentsdb
  • normalized package name match
  • 匹配方式:Opentsdb
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/op/opentsdb/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • 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