# Issues page

The Issues page provides a detailed view of active and resolved issues triggered by Monitors. This page helps users investigate, analyze, and resolve problems in their environment by visualizing issue trends and providing in-depth context through an issue drawer.

## Issues drawer

Clicking on an issue in the Issues List opens the Issue drawer, which provides an in-depth view of the Monitor and its triggered issue. You can also navigate if possible to related entities like workload, node, pod, etc.

<figure><img src="/files/JOFWutugFMTwUfXnwBwG" alt=""><figcaption></figcaption></figure>

### Details tab

Displays metadata about the issue, including:

* **Monitor Name:** Name of the Monitor that triggered the issue, including a link to it.
* **Description:** Explains what the Monitor tracks and why it was triggered.
* **Severity:** Shows the assigned severity level (e.g., S3).
* **Labels:** Lists contextual labels like `cluster`, `namespace`, and `workload`.
* **Creation Time:** Shows when the issue started firing.

### **Events tab**

Displays the Kubernetes events related to the selected issue within the timeframe selected in the Time Picker dropdown (upper right of the issue drawer).

### **Traces tab**

When creating a Monitor using a traces query, the Traces tab will display the matching traces generated within the timeframe selected in the Time Picker dropdown (upper right of the issue drawer). Click on "View in Traces" to navigate to the Traces section with all relevant filters automatically applied.

### **Logs tab**

When creating a monitor using a log query, the Logs tab will display the matching logs generated within the timeframe selected in the Time Picker dropdown (upper right of the issue drawer). Click on "View in Logs" to navigate to the Logs section with all relevant filters automatically applied.

### **Map tab**

A focused visualization of the interactions between workloads related to the selected issue.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.groundcover.com/use-groundcover/monitors/issues-page.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.