--- title: Monitoring description: The Monitoring tab collects a service's SLOs, cases, and alerts in one place, across three switchable panels - SLOs, Cases, and Alert Definitions - so you can see the service's reliability targets and open issues without leaving APM. url: https://coralogix.com/docs/user-guides/apm-v2/features/monitoring/ product: apm feature: APM Overview feature_id: apm-general feature_identifier: apm/apm-general last_updated: '2026-10-15' --- # Monitor a service The **Monitoring** tab collects what watches a service - its service-level objectives (SLOs), the cases open on it, and the alerts scoped to it - so you can see the service's reliability targets and its open issues without leaving APM. The tab has three panels, switched with a toggle that shows a count on each: **SLOs** (the default), **Cases**, and **Alert Definitions**. Monitoring is available for services. Use it to: * **Track reliability targets**: watch each SLO's status, compliance against target, and remaining error budget for the service. * **See what's firing**: scan the alerts scoped to the service, their type and priority, and when each last triggered. * **Reach the case behind an alert**: a firing alert has already opened a case: open its row to jump to the case and start responding. * **Enable or silence an alert in place**: flip a rule on or off from the table without leaving the tab. [![The Monitoring tab\'s SLOs panel: the SLOs / Alerts \& Cases switcher, a health calendar and seven-day SLO status chart, and the SLO table with status, window, target, current state, and remaining budget.](/docs/assets/images/monitoring-slos-160e8fb863b27c97b48b5a258413faaf.webp)](https://coralogix.com/docs/assets/images/monitoring-slos-160e8fb863b27c97b48b5a258413faaf.webp) ## 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. * Monitoring is available for services. Databases do not show the tab. ## Access the Monitoring tab 1. In your Coralogix toolbar, select **APM**. 2. Select a service to open its drilldown, then select the **Monitoring** tab. 3. Use the switcher at the top of the tab to move between the **SLOs**, **Cases**, and **Alert Definitions** panels. Each button shows a count of the items in that panel; the tab opens on **SLOs**. If you open the tab for a database, it shows *Monitoring is available for services only.* ## SLOs The **SLOs** panel lists the [service-level objectives](https://coralogix.com/docs/user-guides/apm-v2/features/service-slos.md) defined for the service in the SLO Center, with each objective's status, evaluation window, target, current compliance, and remaining error budget. When the service has at least one SLO, a status-overview widget sits above the table: a health calendar and a seven-day status chart that summarize how the service's SLOs have tracked over the recent period. The SLO table shows: * **Name**: the SLO's name. * **Status**: the worst status across the SLO's permutations: **Healthy**, **Warning**, **Critical**, **Breached**, or **Pending**. * **Threshold**: the threshold a request must meet to count as good. Latency SLOs only; other SLOs show an em dash. * **Window**: the rolling evaluation window, such as *7 days*. * **Target**: the compliance target for the SLO. * **Current state**: current compliance for the SLO. * **Remaining budget**: the error budget left before the SLO breaches, shown as a bar that fills to the remaining percentage. Use **Search SLOs…** to find one by name, the **All** / **OK** / **Breached** filter to narrow by status, and any column header to sort. Select a row to open the SLO in a drilldown drawer - an **SLO Overview** with compliance over time, remaining error budget, total and good events, and a per-minute snapshot. To open the full **SLO Center** instead, select **Go to SLO Center**. If you have permission to edit SLOs, the toolbar also offers **+ Add SLO**, which opens the SLO Center create drawer with the service pre-filled. This action may not appear for all accounts. See [Service SLOs](https://coralogix.com/docs/user-guides/apm-v2/features/service-slos.md). ## Cases The **Cases** panel lists the cases that affected this service - any case active at some point in the selected time range, not only those opened inside it. When you have environments selected on the page, the table narrows to cases carrying one of those environments; cases with no environment are left out. [![The Cases panel in the Monitoring tab, showing cases with their status, priority, environment, notification destinations, and grouping key.](/docs/assets/images/monitoring-cases-0b7fff54cc552b924ec561c97bd64b8a.webp)](https://coralogix.com/docs/assets/images/monitoring-cases-0b7fff54cc552b924ec561c97bd64b8a.webp) The table shows: * **Case**: the case's readable ID and title. * **Status**: where the case is in its lifecycle: **Pending**, **Active**, **Acknowledged**, **Resolved**, or **Closed**. * **Priority**: the priority the case was opened at, **P1** to **P5**. * **Assignee**: the user the case is assigned to, or **Unassigned**. * **Environment**: the environments of the service the case affects. * **Notifications**: where the case was sent. Select a destination to open it - a Slack message, a PagerDuty or ServiceNow incident, a Microsoft Teams message, or a connector delivery. * **Grouping key**: the labels the case is grouped by. * **Created**: when the case was opened. * **Updated**: when the case last changed. Use **Search cases…** to find one by title or ID, and the **All** / **Active** filter to narrow by status, where **Active** covers the Active, Acknowledged, and Pending states. The table opens sorted by **Updated**, newest first. The filter and sort travel in the URL, so a shared link reopens the table the way you had it. Select a row to open the case in a drawer without leaving APM. To open the full case feed for the service instead, select **Go to Cases**. ## Alert definitions The **Alert Definitions** panel lists the alerts scoped to the service. [![The Alert Definitions table in the Monitoring tab, showing each alert\'s name, status, type, priority, last triggered time, labels, and an inline Enabled toggle.](/docs/assets/images/monitoring-alerts-f3e0875ac293c350beca218a29efd8d9.webp)](https://coralogix.com/docs/assets/images/monitoring-alerts-f3e0875ac293c350beca218a29efd8d9.webp) The table shows: * **Name**: the alert's name. * **Status**: whether the alert is firing right now: **Alerting** or **OK**. * **Type**: the rule type the alert evaluates, such as *Metric - Threshold*, *Logs - Anomaly*, or *Tracing - Threshold*. * **Priority**: the priority the alert notifies at. * **Last triggered**: when the alert last fired, or *Never triggered*. * **Labels**: the entity labels attached to the alert. * **Enabled**: an inline toggle for whether the rule is currently evaluating. Flip it to enable or disable the alert without leaving the tab. Use **Search alerts…** to find one by name and the **All** / **Alerting** / **OK** filter to narrow by status. What a row opens depends on the alert's status: * **A firing alert** (**Alerting**) offers a **View cases** action that opens the case feed for the service, filtered to its APM labels, where you can work the incident. The same **View cases** action is available from a row's action menu in the **Health** tab. * **Any other alert** opens the alert's drilldown in a new tab. To open the full [Alerts](https://coralogix.com/docs/user-guides/alerting/introduction-to-alerts.md) screen, select **Go to Alerts**. To create an alert prefilled from a service's metrics, see [APM monitoring with alerts](https://coralogix.com/docs/user-guides/apm-v2/features/monitoring-with-alerts.md). Note If you don't have permission to view SLOs or alerts, the corresponding panel shows a message instead of the table. Enabling or disabling an alert also requires permission; without it, the **Enabled** toggle is disabled. The **Cases** table needs permission to read cases; without it, the table doesn't appear. ## Next steps Define a reliability target for the service in [Service SLOs](https://coralogix.com/docs/user-guides/apm-v2/features/service-slos.md). ## Additional resources * [Service SLOs](https://coralogix.com/docs/user-guides/apm-v2/features/service-slos.md) * [APM monitoring with alerts](https://coralogix.com/docs/user-guides/apm-v2/features/monitoring-with-alerts.md) * [Cases](https://coralogix.com/docs/user-guides/cases/overview.md)