Copy as Markdown[Open in ChatGPT](https://chatgpt.com/?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Fapm-v2%2Ffeatures%2Fmonitoring-with-alerts.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)[Open in Claude](https://claude.ai/new?q=Read%20https%3A%2F%2Fcoralogix.com%2Fdocs%2Fuser-guides%2Fapm-v2%2Ffeatures%2Fmonitoring-with-alerts.md%20and%20help%20me%20with%20my%20question%20about%20this%20Coralogix%20documentation%20page.)

# APM monitoring with alerts

Create alerts straight from a service's APM metrics, so a rule inherits the query behind the chart you are looking at instead of being built from scratch. APM prefills the alert with a metric-threshold query scoped to the service, and the alerts - and the cases they open - surface back in APM: in the service's **Monitoring** tab and as columns in the [catalog](https://coralogix.com/docs/user-guides/apm-v2/services.md).

Use it to:

* **Alert on what you see**: turn a service's Requests, Errors, or Latency card into a metric alert with the query prefilled.
* **Keep alerts correlated with the service**: prefilled APM labels tie each alert and its cases back to the service.
* **Track status from the catalog**: read a service's **Alerts**, **Cases**, and **SLO status** columns at a glance.
* **Work the issue in one place**: open the case behind a firing alert from the Monitoring tab.

<!-- -->

## What you need[​](#what-you-need "Direct link to What you need")

* Coralogix [Application Performance Monitoring (APM)](https://coralogix.com/docs/user-guides/apm-v2/getting-started/apm-onboarding-tutorial.md) installed and configured.
* [Span Metrics](https://coralogix.com/docs/user-guides/apm-v2/getting-started/span-metrics.md) enabled for the service.
* Permission to manage alerts. Creating alerts from a card is available for services.

## Create an alert from a service's metrics[​](#create-an-alert-from-a-services-metrics "Direct link to Create an alert from a service's metrics")

The service **Overview** exposes three metric cards - **Requests**, **Errors**, and **Latency**. Each card's menu includes **Create alert** (services only):

1. In your Coralogix toolbar, select **APM**, then select a service to open its drilldown.
2. On the **Overview** tab, find the **Requests**, **Errors**, or **Latency** card.
3. Open the card's **More actions** menu () and select **Create alert**.
4. The alert editor opens in create mode, prefilled as a **Metric - Threshold** alert. Its query is generated from that card, scoped to the current service, your selected environments, and the card's active group-by. You can keep the query or adjust it.
5. Define the remaining conditions and notification settings, then create the alert. The editor is part of [Alerting](https://coralogix.com/docs/user-guides/alerting/create-an-alert/metrics/threshold-alerts.md): see that reference for the full alert definition.

Alerts created this way carry APM labels - the product and the service name - so they appear in the [Alerts](https://coralogix.com/docs/user-guides/alerting/introduction-to-alerts.md) screen with the service attached, and they surface back in the service's Monitoring tab.

Note

You can also add service or database catalog labels to alerts you create outside APM. Those alerts are then classified as APM alerts and shown in the relevant APM surfaces. Don't modify the APM labels, or the alert loses its correlation with the service.

## Track alerts, cases, and SLO status[​](#track-alerts-cases-and-slo-status "Direct link to Track alerts, cases, and SLO status")

### In the catalog[​](#in-the-catalog "Direct link to In the catalog")

The [Catalog](https://coralogix.com/docs/user-guides/apm-v2/services.md) has three per-service columns:

* **Alerts**: the alerts scoped to the service.
* **Cases**: the cases open on the service. A firing alert opens a case.
* **SLO status**: the service's SLO health.

### In the Monitoring tab[​](#in-the-monitoring-tab "Direct link to In the Monitoring tab")

Open a service's [Monitoring](https://coralogix.com/docs/user-guides/apm-v2/features/monitoring.md) tab and switch to the **Alerts & Cases** panel to see every alert scoped to the service, enable or disable a rule inline, and open the case behind a firing alert.

Because a firing alert has already opened a case, there is no separate incidents view in APM - the alert row is the way in. Selecting a firing alert opens its case feed for the service; selecting any other alert opens the alert definition. To work the incident in full, open the case from the alert row or go to [Cases](https://coralogix.com/docs/user-guides/cases/overview.md).

## Next steps[​](#next-steps "Direct link to Next steps")

See how a service interacts with its downstream systems in [Dependencies](https://coralogix.com/docs/user-guides/apm-v2/features/dependencies.md).