|
|
|
@ -1,21 +1,20 @@
|
|
|
|
|
# Prometheus |
|
|
|
|
|
|
|
|
|
Bedecke deinen Himmel, Zeus! A new kid is in town. |
|
|
|
|
|
|
|
|
|
Prometheus is a generic time series collection and computation server that is |
|
|
|
|
useful in the following fields: |
|
|
|
|
|
|
|
|
|
* Industrial Experimentation / Real-Time Behavioral Validation / Software Release Qualification |
|
|
|
|
* Econometric and Natural Sciences |
|
|
|
|
* Operational Concerns and Monitoring |
|
|
|
|
|
|
|
|
|
The system is designed to collect telemetry from named targets on given |
|
|
|
|
intervals, evaluate rule expressions, display the results, and trigger an |
|
|
|
|
action if some condition is observed to be true. |
|
|
|
|
|
|
|
|
|
TODO: The above description is somewhat esoteric. Rephrase it into |
|
|
|
|
something that tells normal people how they will usually benefit from |
|
|
|
|
using Prometheus. |
|
|
|
|
Prometheus is a systems and service monitoring system. Prometheus' main |
|
|
|
|
distinguishing features as compared to other monitoring systems are: |
|
|
|
|
|
|
|
|
|
- a **multi-dimensional** data model (timeseries defined by metric name and set of key/value dimensions) |
|
|
|
|
- a **flexible query language** to leverage this dimensionality |
|
|
|
|
- no dependency on distributed storage; **single server nodes are autonomous** |
|
|
|
|
- timeseries collection happens via a **pull model** over HTTP |
|
|
|
|
- **pushing timeseries** is supported via an intermediary gateway |
|
|
|
|
- targets are discovered via **service discovery** or **static configuration** |
|
|
|
|
- multiple modes of **graphing and dashboarding support** |
|
|
|
|
- **federation support** coming soon |
|
|
|
|
|
|
|
|
|
Prometheus collects metrics from configured targets at given intervals, |
|
|
|
|
evaluates rule expressions, displays the results, and can trigger alerts |
|
|
|
|
if some condition is observed to be true. |
|
|
|
|
|
|
|
|
|
## Install |
|
|
|
|
|
|
|
|
|