Prometheus alternatives and similar libraries
Based on the "Monitoring" category.
Alternatively, view prometheus alternatives based on common mentions on social networks and blogs.
9.0 8.6 L4 Prometheus VS MetricsExpose metrics via JMX or HTTP and can send them to a database.
7.1 5.9 L4 Prometheus VS jmxtransTool to connect to multiple JVMs and to query them for their attributes via JMX. Its query language is based on JSON, which allows non-Java programmers to access the JVMs attributes. Likewise, this tool supports different output writes, including Graphite, Ganglia, StatsD, among others.
6.9 0.3 L4 Prometheus VS StagemonitorOpen source performance monitoring and transaction tracing for JVM apps.
4.9 0.0 Prometheus VS inspectITCaptures detailed run-time information via hooks that can be changed on the fly. It supports tracing over multiple systems via the OpenTracing API and can correlate the data with end user monitoring.
2.6 0.0 Prometheus VS Failsafe ActuatorOut of the box monitoring of Failsafe Circuit Breaker in Spring-Boot environment.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest. Visit our partner's website for more details.
Do you think we are missing an alternative of Prometheus or a related project?
Visit prometheus.io 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
There are various ways of installing Prometheus.
Precompiled binaries for released versions are available in the download section on prometheus.io. Using the latest production release binary is the recommended way of installing Prometheus. See the Installing chapter in the documentation for all the details.
You can launch a Prometheus container for trying it out with
$ docker run --name prometheus -d -p 127.0.0.1:9090:9090 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 Yarn installed in order to build the frontend assets.
You can directly use the
go tool to download and install the
promtool binaries into your
$ GO111MODULE=on go get github.com/prometheus/prometheus/cmd/... $ prometheus --config.file=your_config.yml
However, when using
go get to build Prometheus, Prometheus will expect to be able to
read its web assets from local filesystem directories under
web/ui/templates. 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 or
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/github.com/prometheus $ cd $GOPATH/src/github.com/prometheus $ git clone https://github.com/prometheus/prometheus.git $ cd prometheus $ make build $ ./prometheus --config.file=your_config.yml
The Makefile provides several targets:
- build: build the
promtoolbinaries (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 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 [README.md](web/ui/react-app/README.md).
- The source code is periodically indexed: Prometheus Core.
- You will find a CircleCI configuration in [
- See the Community page for how to reach the Prometheus developers and users on various communication channels.
Refer to CONTRIBUTING.md
Apache License 2.0, see LICENSE.
*Note that all licence references and agreements mentioned in the Prometheus README section above are relevant to that project's source code only.