Prometheus and Mite

Mite is designed to output the data on its performance tests to prometheus (for storage, indexing, and machine-readable retrievability) and then grafana (for data visualization and analysis). In the following sections, weʼll discuss some of the details involved in configuring these applications.

Prometheus

Prometheus collects its metrics by scraping an http endpoint at a defined interval. It should be configured to point to port 9301 on the machine where the mite prometheus_exporter command runs. Here is a minimal prometheus.yml config file:

global:
  scrape_interval: 1s

scrape_configs:
  - job_name: 'mite'
    static_configs:
      - targets: ['127.0.0.1:9301']

The targets is configured on the assumption that the prometheus process runs on the same machine as the mite exporter process. If this is not the case, you will have to change the localhost IP to an actual IP or hostname (as well as making sure that the mite instance is accessible to the prometheus from a firewall perspective).

Grafana

The grafana instance you are using will need to be set up with your prometheus as a data source. The Prometheus documentation has an example of how to accomplish this. We provide a dashboard (TODO link to be updated) which is pre-configured for mite. The dashboard assumes that you have several applications under test, which will have their measurements tagged in Prometheus with an application label. You will need to edit the dashboard variables so that they reflect the names of your applications. (Otherwise, you can take out the application=~$app query from all the dashboard panels). As the grafana documentation points out, you will also need to edit the datasource of the dashboard to match the prometheus instance you configured grafana with.