> ## Documentation Index
> Fetch the complete documentation index at: https://metoro.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Issues

> Track recurring issues that Metoro has identified across its AI investigation workflows, their investigation history, and related remediation work

## Overview

**Issues** is the durable list of production issues that Metoro has identified across its AI investigation workflows.

Instead of treating each investigation as an isolated event, Metoro groups repeated recurrences of the same underlying problem into a single issue so your team can track status, history, and follow-up work in one place.

<img src="https://mintcdn.com/metoro/w4X7_lLX94MSPRwF/images/ai_sre_issue_catalog.png?fit=max&auto=format&n=w4X7_lLX94MSPRwF&q=85&s=dea94237c3c1b8a7b435778b2ff38ffe" alt="Issues Catalog" width="4608" height="2592" data-path="images/ai_sre_issue_catalog.png" />

From the **Issues** page, you can:

* See which production problems are still open
* Prioritize by severity and recurrence
* Review the latest investigation behind an issue
* Follow related code fixes and remediation work over time

## How Issues Work

When Metoro determines that an investigation reflects a real production issue, it can **create** or **update** an issue. Each issue becomes a long-lived record of that underlying problem, including:

* A title and summary
* Open or closed status
* Priority (`P1`, `P2`, `P3`)
* Category (`application` or `infrastructure`)
* Affected services and environments
* Recurrence history and last seen time
* Links to related investigations and generated code fixes

## Issue Details

Opening an issue gives you the full context Metoro has accumulated about that problem.

<img src="https://mintcdn.com/metoro/w4X7_lLX94MSPRwF/images/ai_sre_issue_example.png?fit=max&auto=format&n=w4X7_lLX94MSPRwF&q=85&s=9aa50af27dc63efbbff35d497bdd155f" alt="Issues Catalog" width="4608" height="2592" data-path="images/ai_sre_issue_example.png" />

The issue details view includes:

* The issue description and current status
* Created time and last seen time
* Environment, namespace, service, and category
* A recurrence trend and status journey
* An event timeline showing related investigations and activity
* Related resources such as the most recent investigation and any generated code fix

You can also mark an issue as closed or reopen it later if the same problem needs active follow-up again.

## Notifications

If you want your team to be notified when Metoro creates a new issue, you can use the Issue Notification feature.
Go to **Settings** → **Features** → **Issue Detection** to set up notification filters and channels.

[Take me there](https://us-east.metoro.io/settings?tab=features\&subtab=issue-detection)

[Learn more about AI SRE notifications →](/ai-sre/notifications)

## Related Docs

<CardGroup cols={2}>
  <Card title="AI SRE Overview" icon="sparkles" href="/ai-sre/overview">
    Understand how AI SRE fits into Metoro's broader workflows.
  </Card>

  <Card title="Autonomous Issue Detection" icon="magnifying-glass" href="/ai-sre/anomaly-detection">
    Learn how Metoro detects abnormal behavior and investigates it automatically.
  </Card>

  <Card title="AI Alert Investigations" icon="bell" href="/ai-sre/alert-investigations">
    Investigate firing alerts and continue to root cause when needed.
  </Card>

  <Card title="Code Fixes" icon="code" href="/ai-sre/github-integration">
    Add code context and generated fixes to investigations and issues.
  </Card>
</CardGroup>