# Migrating from Issues to Monitors Issues Page

The legacy Issues page is being deprecated in favor of a fully customizable, monitor-based experience that gives you more control over what constitutes an issue in your environment.

While the new page introduces powerful capabilities, no core functionality is being removed, the key change is that the old auto-created issue rules will no longer be automatically generated. Instead, you’ll define your own monitors, or choose from a rich catalog of prebuilt ones.

All the existing issues in the legacy page can be easily added to the monitors via the Monitors Catalog's "Started Pack". See [Getting Started](#getting-started) below for more info.

### Why migrate to the new Issues experience?

The new Issues page is built on top of the Monitors engine, enabling deeper customization and automation:

1. **Define what qualifies as an issue**

   Use filters in monitor definitions to include or exclude workloads, namespaces, HTTP status codes, clusters, and more tailor it to your context.
2. **Silence issues with precision**

   Silence issues based on any label, such as `status_code`, `cluster`, or `workload`, to reduce noise and keep focus.
3. **Clean, scoped issue view**

   Only see issues relevant to your environment, based on your configured monitors and silencing rules, no clutter.
4. **Get alerted on new issues**

   Trigger alerts through your preferred integrations (Slack, PagerDuty, Webhooks, etc.) when a new issue is detected.
5. **Define custom issues using all your data**

   Build monitors using metrics, traces, logs, and events, and correlate them to uncover complex problems.
6. **Manage everything as code**

   Use Terraform to manage monitors and issues at scale, ensuring consistency and auditability.

### What’s Changing?

| Aspect                              | Legacy Issues Page | New Issues Page       |
| ----------------------------------- | ------------------ | --------------------- |
| Issue Source                        | Auto-created rules | User-defined monitors |
| Custom Filtering                    | ❌                  | ✅                     |
| Silencing by Labels                 | ❌                  | ✅                     |
| Alerts via Integrations             | ❌                  | ✅                     |
| Terraform Support                   | ❌                  | ✅                     |
| Issues Based on Traces/Logs/Metrics | Limited            | Full support          |

### Getting Started

All the built-in rules you’re used to are already available in the [Monitors Catalog](/use-groundcover/monitors/monitor-catalog-page.md), you can add them all with a single click.

Adding the monitors in the "Started Pack" will match all the existing issues in the legacy page.

Head to:

**Monitors → Create Monitor -> Monitor Catalog → Recommended Monitors**

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

{% hint style="info" %}
Only users with Editor/Admin roles can create monitors
{% endhint %}

### Learn More

* [Create a new Monitor](/use-groundcover/monitors/create-a-new-monitor.md)
* [Issues page](/use-groundcover/monitors/issues-page.md)
* [Silences page](/use-groundcover/monitors/silences-page.md)


---

# 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/migrating-from-issues-to-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.