# Install opentsdb with Homebrew, Nix

Scalable, distributed Time Series Database. Version 2.4.1 via Homebrew; verified 2026-07-31. Also installable with nix: nix profile install nixpkgs#opentsdb.

## Install

```sh
sudo av install brew:opentsdb
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install opentsdb
```

  Evidence: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#opentsdb
```

  Evidence: nixpkgs package indexes: pkgs/by-name/op/opentsdb/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Package facts

- **Package key:** brew:opentsdb
- **Package manager:** Homebrew
- **Version:** 2.4.1
- **Source summary:** Scalable, distributed Time Series Database
- **Homepage:** <http://opentsdb.net/>
- **Repository:** <https://github.com/OpenTSDB/opentsdb>
- **Last updated:** 2026-07-31T08:47:03+01:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- start-tsdb.sh (alias)
- tsdb (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 2.4.1
## Project history and usage

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.

### Project history

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.

### Adoption history

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.

### How it is used

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.

### Why package nerds care

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.

### Timeline

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

### Sources

- <https://dbdb.io/db/opentsdb>
- <https://github.com/OpenTSDB/opentsdb>
- <https://github.com/OpenTSDB/opentsdb/blob/master/AUTHORS>
- <https://opentsdb.net/>
- <https://opentsdb.net/faq.html>
- <https://opentsdb.net/misc/opentsdb-hbasecon.pdf>
- <https://opentsdb.net/overview.html>
- <https://opentsdb.net/schema.html>


## Security Notes

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

- **Geiger risk:** orange / medium
- broad file, network, media, or database tool signal
- formula declares a Homebrew service


## 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

- Unix: ./opentsdb.conf, /etc/opentsdb.conf, /etc/opentsdb/opentsdb.conf, /opt/opentsdb/opentsdb.conf
## Other Package-Manager Records

- Nix - opentsdb: normalized package name match | nixpkgs package indexes: pkgs/by-name/op/opentsdb/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/opentsdb.yml](https://github.com/mxcl/pkgdb/blob/main/combined/opentsdb.yml)


## Sources

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