Third-Party Services Monitoring

This topic describes how to use dashboards for third-party services.

MySQL

Mysql dashboard header

  1. To track metrics from internal MySQL databases used by PCF Elastic Runtime:

    1. Open the Service - MySQL * dashboards,
    2. Select cf-* from the Deployment drop-down menu,
    3. Select mysql from the Host drop-down menu.
  2. To track metrics from external MySQL databases used by PCF Elastic Runtime:

    1. Open the Service - MySQL * dashboards,
    2. Select cf-* from the Deployment drop-down menu,
    3. Select cloud_controller from the Host drop-down menu.
  3. To track metrics from the MySQL for PCF tile:

    1. Open the Service - MySQL * dashboards,
    2. Select p-mysql-* from the Deployment drop-down menu,
    3. Select mysql from the Host drop-down menu.
  4. To track metrics from an external MySQL installation:

    1. Open the Service - Mysql * dashboards,
    2. Select altoros-heartbeat-* from the Deployment drop-down menu,
    3. Select external-collectd from the Host drop-down menu.

PostgreSQL

Postgresql dashboard header

  1. To track metrics from the Crunchy PostgreSQL (on-demand version) deployment:

    1. Open the Service - PostgreSQL Overview dashboard.
    2. Select service-instance_* from the Deployment drop-down menu.
    3. Select postgresql from the Host drop-down menu.
  2. To track metrics from an internal PostgreSQL databases used by PCF Elastic Runtime:

    1. Open the Service - PostgreSQL Overview dashboard.
    2. Select cf-* from the Deployment drop-down menu.
    3. Select postgres from the Host drop-down menu.
  3. To track metrics from an external PostgreSQL installation:

    1. Open the Service - Postgresql Overview dashboard.
    2. Select altoros-heartbeat-* from the Deployment drop-down menu.
    3. Select name of your PostgreSQL host from the Host drop-down menu.

RabbitMQ

Rabbitmq dashboard header

  1. To track metrics from the RabbitMQ for PCF tile:

    1. Open the Service - RabbitMQ * dashboards.
    2. Select p-rabbitmq-* from the Deployment drop-down menu.
    3. Select rabbitmq-broker from the Host drop-down menu.
  2. To track metrics from an external RabbitMQ installation:

    1. Open the Service - RabbitMQ * dashboards.
    2. Select altoros-heartbeat-* from the Deployment drop-down menu.
    3. Select external-collectd from the Host drop-down menu.

Redis

Redis dashboard header

  1. To track metrics from the Redis for PCF tile:

    1. Open the Service - Redis Overview dashboard.
    2. Select p-redis-* from the Deployment drop-down menu.
    3. Select cf-redis-broker or dedicated-node from the Host drop-down menu.
  2. To track metrics from an external Redis installation:

    1. Open the Service - Redis Overview dashboard.
    2. Select altoros-heartbeat-* from the Deployment drop-down menu.
    3. Select name of your Redis host from the Host drop-down menu.

Elasticsearch

Note: Index stats are sent only from the active master. If you need different configuration, contact Altoros.

Elasticsearch dashboard header

  1. To track metrics from the Altoros Log Search for PCF tile:
    1. Open the Service - Elasticsearch Overview dashboard.
    2. Select logsearch-* from the Deployment drop-down menu.
    3. Select elasticsearch_data or cluster_monitor from the Host drop-down menu.

MongoDB

Mongodb dashboard header

  1. To track metrics from an external MongoDB installation:
    1. Open the Service - MongoDB Overview dashboard.
    2. Select altoros-heartbeat-* from the Deployment drop-down menu.
    3. Select external-collectd from the Host drop-down menu.

Memcached

Memcached dashboard header

  1. To track metrics from an external Memcached installation:
    1. Open the Service - Memcached Overview dashboard.
    2. Select altoros-heartbeat-* from the Deployment drop-down menu.
    3. Select name of your Memcached host from the Host drop-down menu.

Concourse

Configure Concourse web worker (aka ATC) to transfer metrics to Altoros Heartbeat. To do this:

  1. Find the IP address of the Collectd virtual machine that is used to monitor external services:

    1. From the Altoros Heartbeat for PCF tile, select the Status tab.
    2. Scroll down to Collectd VM to monitor external services and copy the IP address in the IPS column.

    External services vm

  2. Run Concourse web worker (aka ATC) using the following CLI parameters or environment variables:

    1. --riemann-host=<COLLECTD-VM-IP-ADDRESS> or CONCOURSE_RIEMANN_HOST=<COLLECTD-VM-IP-ADDRESS>. Use the IP address copied in the previous step.
    2. --metrics-host-name=<CONCOURSE-WEB-WORKER-NAME> or CONCOURSE_METRICS_HOST_NAME=<CONCOURSE-WEB-WORKER-NAME>. Set a name starting with web, for example web-0. This name is used to find metrics in the dashboard.

External concourse grafana header

  1. To track metrics from an external Concourse installation:
    1. Open the Service - External Concourse Overview dashboard.
    2. From the Deployment drop-down menu, select altoros-heartbeat-*.
    3. From the Web Host drop-down menu, select the name of the host configured above.

HAProxy

Haproxy grafana header

  1. To track metrics from the HAProxy that is used by PCF Elastic Runtime:

    1. Open the CF HAProxy* dashboards.
    2. From the Deployment drop-down menu, select cf-*.
    3. From the Host drop-down menu, select ha_proxy.
  2. To track metrics from the HAProxy used by the RabbitMQ for PCF tile:

    1. Open the CF HAProxy* dashboards.
    2. From the Deployment drop-down menu, select p-rabbitmq-*.
    3. From the Host drop-down menu, select rabbitmq-haproxy.
Create a pull request or raise an issue on the source for this page in GitHub