Promregator is looking for contributors/supporters!
Attention Users of Promregator! Influence development of Promregator by answering our polls!
The term "Promregator" is an artifical composite of the two terms "Prometheus" and "aggregator".
Prometheus is referring to the Prometheus project, which is a toolset intended for retrieving telemetry data of running applications. It supports monitoring these metrics and triggering alerts based on thresholds.
Aggregator is referring to the aggregator concept, which you encounter several times in the Platform-as-a-Service offering of Cloud Foundry. The most prominent case of an aggregator in Cloud Foundry most likely is the Loggregator.
The Promregator project intends to provide an aggregator-like tool for the Cloud Foundry environment, which allows fetching Prometheus metrics of a set of Cloud Foundry app instances. Note that it is not the intention to facilitate scraping of metrics on platform level (e.g. for monitoring services, which are exposed via BOSH containers on the Cloud Foundry platform), but support monitoring of metrics on application level (if you are looking for platform monitoring, you might find https://github.com/pivotal-cf/prometheus-on-PCF and https://github.com/bosh-prometheus/prometheus-boshrelease interesting).
If you want to jumpstart and see what Promregator may do, please refer to our quickstart description.
Here is the list of major features provided by Promregator:
Standard Java-Application implemented using the Spring Framework. There is no need for administrative privileges on your Cloud Foundry installation! You can even run Promregator outside of your Cloud Foundry environment (such as behind an internal firewall), as Promregator also supports proxy servers.
Automatic discovery of instances and hostnames of Cloud Foundry apps supported
Fetching of the Prometheus Metric endpoints of multiple app instances is performed in parallel (number of concurrent threads used for retrieving metrics can be configured).
Support of Authentication Schemes at the CF app's endpoint. The following Authentication schemes are currently available:
The available authentication schemes are easily extensible.
(>= 0.4.0) Each target may be configured to use its own authentication scheme, thus you may authenticate to multiple CF apps using different credentials.
(>= 0.2.0) Support for inbound authentication (e.g. Prometheus authenticates to Promregator) using Basic HTTP Authentication.
Configuration using standard Spring properties as defined by the Spring Framework (e.g. using
(>= 0.6.0) Support for encrypted passwords in configuration files including providing the encryption key via Docker Secrets
Simple HTTP proxy support is available for contacting CF app endpoints.
Additional metrics are provided supporting you to monitor Promregator and the communication to the Cloud Foundry applications.
(>= 0.4.0) Cache Invalidation is possible via an (optionally auth-protected) HTTP REST endpoint.
Promregator's endpoints (e.g.
/discovery) support GZIP compression, if the clients indicates to accept it.
Promregator is sitting between your Prometheus server on the one hand and talks to your Cloud Foundry apps on the other hand. It is converting the Prometheus' scraping requests into queries targeting your instances of your apps, which are running on Cloud Foundry.
For further details on the architecture of Promregator, please look at the architecture page.
During the course of action, we came across several other implementation alternatives. Due to one or the other reason they were not implemented. You may find a detailed discussion about these approaches on our discarded ideas page.
Running Promregator requires:
Compiling Promregator additionally requires:
Further dependencies required are automatically loaded when building the software. An internet connection to Maven Central is necessary for that.
Promregator has been released first on 2018-03-18. It currently provides two binary-based deliveries:
Furthermore, you may create your own package by downloading the source code, unpacking it into a local folder and calling
mvn clean package
The runnable artifact will be available at
target/promregator-*-SNAPSHOT.jar. It is a self-contained (e.g. including all library dependencies) JAR file, which can be copied around and executed at an arbitrary folder by calling
java -jar promregator-x.y.z-SNAPSHOT.jar
A detailed documentation, including a description how you may configure Promregator, what needs to be done to integrate it with Prometheus is available at the documentation pages.
For related work, which we came across, refer to our references page.
For sending material (e.g. memory dumps) for analysis, which you do not want to (or even should not) share to/with the public, please refer to our analysis material page