# Bug The `AlertmanagerClusterDown` alert fires, even though Alertmanager is healthy. This happens because Prometheus cannot access the Alertmanager `reloader-web` port, due to lack of an `AuthorizationPolicy` port entry. ## Description With the addition of the [reloader-web](https://repo1.dso.mil/big-bang/product/packages/monitoring/-/commit/40bf1ae0f069cc0b616de3057c991adc68cd9673?page=2#74b8fe051bceb11bbfe5b25535aed7d22981e73f_49_50) port to the [AlertManager ServiceMonitor](https://repo1.dso.mil/big-bang/product/packages/monitoring/-/blob/main/chart/templates/alertmanager/servicemonitor.yaml#L48) configuration, the [AlertmanagerClusterDown](https://repo1.dso.mil/big-bang/product/packages/monitoring/-/blob/main/chart/templates/prometheus/rules-1.14/alertmanager.rules.yaml#L228) alert fires, even when there is a healthy Alertmanger instance. This happens because there are now two service ports to monitor, so the `up` metric is only reporting 1/2 "alertmanagers" healthy. The metric scraping failure happens because the Alertmanager port (9093) has an [AuthorizationPolicy](https://repo1.dso.mil/big-bang/product/packages/monitoring/-/blob/main/chart/templates/bigbang/authorizationpolicies/am-authz-policy.yaml?ref_type=heads#L22) which allows for Prometheus scraping, however, it does not have an entry to allow scraping of the `reloader-web` port (8080). The `reloader-web` port (8080) should be added to the Alertmanager `AuthorizationPolicy` to allow for scraping both service ports. ## BigBang Version What version of BigBang were you running? 2.14.0