Configuring the receiver to forward monitoring data - Adaptive Applications - BlueCat Gateway - 22.1

BlueCat Health Monitoring Administration Guide

English (United States)
Product name
BlueCat Gateway

Additional environment variables can be added to forward monitoring data in a tiered network environment.

In its default state, the BlueCat Health Monitoring receiver processes monitoring data and saves it to the database. In some highly secured networks, either the DNS/DHCP Server or the receiver may not have direct access to the database. This is common with tiered network services configuration. In such cases, it may be necessary to forward monitoring data from one tier to another tier to get processed.

For instance, in a 3 tier network architecture the DNS/DHCP Server resides in Tier 1 where as the BlueCat Health Monitoring application is installed in a Tier 3 network. Tier 1 network can only send data to Tier 2 and/or allowed to send data over a specific port through the firewall between the tiers.

To allow monitoring data to pass through Tier 1 > Tier 2 > Tier 3, BlueCat Health Monitoring receivers can be deployed in all 3 tiers where they forward data from Tier 1 > Tier 2 and then Tier 2 > Tier 3.

This can be achieved by running the BlueCat Health Monitoring portal with the following environment variables:

FORWARD_URI=<Receiver_uri> #http://tier2receiver1/bhm/api/messages:80,http://tier2receiver2/bhm/api/messages:443
  • FORWARD_ROLE: This option is false by default. When setting to true, FORWARD_URI parameter is also needed. Setting this to true will forward monitoring data to configured receivers instead of processing it.
  • FORWARD_URI: This is a comma-separated list of BlueCat Health Monitoring receivers where this receiver will forward the data.

These parameters are added as environment variables to the BlueCat Health Monitoring receiver's docker compose file.

Example receiver-docker-compose.yml:

version: "3"


      - "10045:80"
      - FORWARD_ROLE=true
      - FORWARD_URI=http://receiver:80
    restart: always