Need help with prometheus?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

38.8K Stars 6.3K Forks Apache License 2.0 9.2K Commits 509 Opened issues


The Prometheus monitoring system and time series database.

Services available


Need anything else?

Contributors list


CircleCI Docker Repository on Quay Docker Pulls Go Report Card CII Best Practices Gitpod ready-to-code Fuzzing Status

Visit for the full documentation, examples and guides.

Prometheus, a Cloud Native Computing Foundation project, is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts when specified conditions are observed.

The features that distinguish Prometheus from other metrics and monitoring systems are:

  • A multi-dimensional data model (time series defined by metric name and set of key/value dimensions)
  • PromQL, a powerful and flexible query language to leverage this dimensionality
  • No dependency on distributed storage; single server nodes are autonomous
  • An HTTP pull model for time series collection
  • Pushing time series is supported via an intermediary gateway for batch jobs
  • Targets are discovered via service discovery or static configuration
  • Multiple modes of graphing and dashboarding support
  • Support for hierarchical and horizontal federation

Architecture overview


There are various ways of installing Prometheus.

Precompiled binaries

Precompiled binaries for released versions are available in the download section on Using the latest production release binary is the recommended way of installing Prometheus. See the Installing chapter in the documentation for all the details.

Docker images

Docker images are available on or Docker Hub.

You can launch a Prometheus container for trying it out with

$ docker run --name prometheus -d -p prom/prometheus

Prometheus will now be reachable at http://localhost:9090/.

Building from source

To build Prometheus from source code, first ensure that have a working Go environment with version 1.14 or greater installed. You also need Node.js and npm installed in order to build the frontend assets.

You can directly use the

tool to download and install the
binaries into your
$ GO111MODULE=on go install
$ prometheus --config.file=your_config.yml

However, when using

go install
to build Prometheus, Prometheus will expect to be able to read its web assets from local filesystem directories under
. In order for these assets to be found, you will have to run Prometheus from the root of the cloned repository. Note also that these directories do not include the new experimental React UI unless it has been built explicitly using
make assets
make build

An example of the above configuration file can be found here.

You can also clone the repository yourself and build using

make build
, which will compile in the web assets so that Prometheus can be run from anywhere:
$ mkdir -p $GOPATH/src/
$ cd $GOPATH/src/
$ git clone
$ cd prometheus
$ make build
$ ./prometheus --config.file=your_config.yml

The Makefile provides several targets:

  • build: build the
    binaries (includes building and compiling in web assets)
  • test: run the tests
  • test-short: run the short tests
  • format: format the source code
  • vet: check the source code for common errors
  • assets: build the new experimental React UI

Building the Docker image


make docker
target is designed for use in our CI system. You can build a docker image locally with the following commands:
$ make promu
$ promu crossbuild -p linux/amd64
$ make npm_licenses
$ make common-docker-amd64

NB if you are on a Mac, you will need gnu-tar.

React UI Development

For more information on building, running, and developing on the new React-based UI, see the React app's

More information


Refer to


Apache License 2.0, see LICENSE.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.