Set Up Monitoring

1. Open the Expert Editor.
2. Navigate to /monitoring/prometheus/prometheus.yml.
3. In the scrape_configs section, find the mta scrape job, and replace example-mta1/2 with the hostnames of your MTA VMs. If you have more MTAs, add more targets with correct hostnames.
   prometheus.yml

     - job_name: mta
       scheme: https
       tls_config:
         insecure_skip_verify: true
       metrics_path: /federate
       params:
         match[]:
         - '{job!=""}'
       static_configs:
       - targets:
         - example-mta1:9090
       - targets:
         - example-mta2:9090
   

4. Click Publish. The monitoring configuration becomes active within about one minute; after a few minutes you should start to see data in the monitoring dashboards.

​

Set up more than two MTAs

1. Navigate to /monitored_mta/prometheus/.
2. Duplicate an existing prometheus.yml.vmx.N file once for each additional MTA.
3. For every additional prometheus.yml.vmx.N: Change external_labels.host to the name of the respective MTA, e.g. mta3.
   prometheus.yml.vmx.N

   global:
   #  (...)
     external_labels:
       host: mta3
   

   Note: Setting the host label in monitored_mta/prometheus/prometheus.yml.vmx.N as opposed to setting them centrally in the XCC Prometheus config, i.e. monitoring/prometheus/prometheus.yml, allows alerts generated on the MTAs to display their own hostname by using {{ $labels.host }} in the alert template.
4. Navigate to /monitored_mta/promtail/.
5. Duplicate an existing config.yml.vmx.N file once for each additional MTA.
6. For every additional config.yml.vmx.N: Update the hosts label to match the MTA:
   config.yml.vmx.N

   #  (...)
   labels:
     job: docker-logs
     host: <label>
   

7. Click Publish. The monitoring configuration becomes active within about one minute.

​

Set up Sandbox monitoring

1. Open monitoring/prometheus/prometheus.yml.
2. In the scrape_configs section, add the following dana job to the end. Set a unique <HOSTX> value for each target.
   prometheus.yml

     - job_name: dana
       scrape_interval: 1m
       scheme: https
       tls_config:
           insecure_skip_verify: true
       metrics_path: /noauth/metrics
       static_configs:
           - targets: [ dana1.example.com:443 ]
           labels:
               host: Dana.<HOST1>
           - targets: [ dana2.example.com:443 ]
           labels:
               host: Dana.<HOST2>
   
3. In the same file, scroll up and add dana_alerts.yml to rule_files to activate alert rules for the Sandbox:
   prometheus.yml

     rule_files:
       # Default alerting rules
       - /config/monitoring/prometheus/alert/monitoring_alerts.yml
       - /config/monitoring/prometheus/alert/system_alerts.yml
       - /config/monitoring/prometheus/alert/xcc_alerts.yml  
       - /config/monitoring/prometheus/alert/dana_alerts.yml          # add this line
   

   Sandbox AlertsSandbox alerts will trigger on the XCC. As a consequence, if XCC is down, no Sandbox alerts will be created (in contrast to the MTA alerts that are triggered on the MTAs).
   
4. Navigate to monitoring/grafana/provisioning/dashboards/ and open custom.yml
5. Uncomment the DANA Dashboards:
6. Click Publish. The monitoring configuration becomes active within about one minute.