> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-kubernetes/5.13/bareos-what-is-bareos/catapult-rules-alarms/environment-status-monitoring.md).

# Environment Status Monitoring

Environment status represents the state of the cluster and nodes as seen within the SaaS Management Plane.

Below is the YAML-based rule set that Catapult uses, including alert names, expression, timeframe, labels with type and severity, and annotations which contain the summary and description of the notification.

{% tabs %}
{% tab title="YAML" %}

```yaml
bash-5.0# cat qbert.yml
groups:
  - name: qbert
    rules:
      - alert: ClusterStatusNotOK
        expr: qbert_cluster_status_ok{job="qbert"} == 0
        for: 10m
        labels:
          type: pf9
          severity: warning
        annotations:
          summary: Cluster status is not ok!
          description: Cluster status of {{ $labels.cluster_name }} of type {{ $labels.cloud_provider_type }} is not ok

      - alert: NodeNotReady
        expr: qbert_kube_node_ready{node_status!="Ready", cluster_name!="undefined"} == 0
        for: 10m
        labels:
          type: pf9
          severity: warning
        annotations:
          summary: Node {{ $labels.node_name }} is not ready!
          description: Node {{ $labels.node_name }} cluster {{ $labels.cluster_name }} role {{ $labels.node_role }} is in state {{ $labels.node_status }}

      - alert: K8sApiNotResponding
        expr: qbert_node_status_ok{node_role="master"} == 0
        for: 10m
        labels:
          type: pf9
          severity: warning
        annotations:
          summary: K8s api of cluster {{ $labels.cluster_name }} is not responding!
          description: K8s api is not responding on cluster {{ $labels.cluster_name }} Node {{ $labels.node_hostname }} role {{ $labels.node_role }}

      - alert: WorkerNodeNotResponding
        expr: qbert_node_status_ok{node_role="worker"} == 0
        for: 15m
        labels:
          type: pf9
          severity: warning
        annotations:
          summary: Worker node not responding!
          description: Worker node not responding on cluster {{ $labels.cluster_name }} Node {{ $labels.node_hostname }} role {{ $labels.node_role }}
bash-5.0#
```

{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.platform9.com/managed-kubernetes/5.13/bareos-what-is-bareos/catapult-rules-alarms/environment-status-monitoring.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.