The RBAC module is effectively a proxy that sits in front of the Prometheus client pod. It  examines the requests for authorization headers, and at that point, enforces role-based  controls. It does this by retrieving the users current IBM Cloud Private access token, retrieved  when logging in to the IBM Cloud Private dashboard. From the access token, the proxy can  identify the user and their roles, and use this information to filter the query results, ensuring  users can only see metrics they are authorized to see. Alerting with Prometheus is separated into two parts. Alerting rules in Prometheus servers  send alerts to an Alertmanager. The Alertmanager then manages those alerts, including  silencing, inhibition, aggregation and sending out notifications via methods such as: The rule manager in Prometheus is responsible for evaluating recording and alerting rules on  a periodic basis (as configured using the evaluation_interval configuration file setting). It  evaluates all rules on every iteration using PromQL and writes the resulting time series back  into the storage. The notifier takes alerts generated by the rule manager via its Send()  method, enqueues them, and forwards them to all configured Alertmanager instances. The  notifier serves to decouple generation of alerts from dispatching them to Alertmanager (which  may fail or take time). The Alertmanager handles alerts sent by client applications such as the Prometheus server. It  takes care of deduplicating, grouping, and routing them to the correct receiver integration.  The following describes the core concepts the Alertmanager implements: Grouping -  Grouping categorizes alerts of similar nature into a single notification. This is  especially useful during larger outages when many systems fail at once and hundreds to  thousands of alerts may be firing simultaneously. Inhibition -  Inhibition is a concept of suppressing notifications for certain alerts if certain  other alerts are already firing. Silences -  Silences are a straightforward way to simply mute alerts for a given time. A silence  is configured based on matchers, just like the routing tree. Incoming alerts are checked  whether they match all the equality or regular expression matchers of an active silence. If they  do, no notifications will be sent out for that alert. For more information on Alertmanager refer the url below: https://prometheus.io/docs/alerting/overview/ Grafana includes built-in support for Prometheus. Grafana exposes metrics for Prometheus  on the  /metrics  endpoint. IBM Cloud Private comes with a Grafana dashboard to display the  health status and various metrics about the cluster. Users can access the Prometheus UI  directly at  https://<master-ip>:8443/prometheus . 5.3.3 How Grafana works 5.3.2 How AlertManager works GLYPH<SM590000> Email GLYPH<SM590000> Generic Webhooks GLYPH<SM590000> HipChat GLYPH<SM590000> OpsGenie GLYPH<SM590000> PagerDuty GLYPH<SM590000> Pushover GLYPH<SM590000> Slack Chapter 5. Logging and monitoring  225