---
title: Service Health tab
description: How to use the Service Health tab, which tracks metrics for how quickly a deployment responds to prediction requests to find bottlenecks and assess capacity.

---

# Service Health tab {: #service-health-tab }

The **Service Health** tab tracks metrics about a deployment's ability to respond to prediction requests quickly and reliably. This helps identify bottlenecks and assess capacity, which is critical to proper provisioning.

For example, if a model seems to have generally slowed in its response times, the **Service Health** tab for the model's deployment can help. You might notice in the tab that median latency goes up with an increase in prediction requests. If latency increases when a new model is switched in, you can consult with your team to determine whether the new model can instead be replaced with one offering better performance.

To access **Service Health**, select an individual deployment from the deployment inventory page and, from the resulting **Overview** page, choose the **Service Health** tab. The tab provides informational [tiles](#understanding-the-metric-tiles) and a [chart](#understanding-the-service-health-chart) to help assess the activity level and health of the deployment.

![](images/deploy-service-health-1.png)

{% include 'includes/service-health-prediction-time.md' %}

##  Use the time range and resolution dropdowns {: #use-the-time-range-and-resolution-dropdowns }

The controls&mdash;model version and data time range selectors&mdash;work the same as those available on the [**Data Drift**](data-drift#use-the-time-range-and-resolution-dropdowns) tab. The **Service Health** tab also supports [segmented analysis](deploy-segment), allowing you to view service health statistics for individual segment attributes and values.

![](images/service-health-selectors.png)

##  Understand the metric tiles {: #understand-the-metric-tiles }

DataRobot displays informational statistics based on your current settings for model and time frame. That is, tile values correspond to the same units as those selected on the slider. If the slider interval values are weekly, the displayed tile metrics show values corresponding to weeks. Clicking a metric tile updates the chart below.

**Service Health** reports on the following metrics:

| Statistic |   Reports for selected time period... |
|-------------------|-------------------------|
| Total Predictions | The number of *predictions* the deployment has made.  |
| Total Requests    | The number of prediction requests the deployment has received (a single request can contain multiple prediction requests).  |
| Requests over...  | The number of requests where the response time was longer than the specified number of milliseconds. The default is 2000 ms; click in the box to enter a time between 10 and 100,000 ms or adjust with the controls. |
| Response Time  | The time (in milliseconds) DataRobot spent receiving a prediction request, calculating the request, and returning a response to the user. The report does not include time due to network latency. Select the median prediction request time or 90th, 95th, or 99th percentile. The display reports a dash if you have made no requests against it or if it's an external deployment. |
| Execution Time  | The time (in milliseconds) DataRobot spent calculating a prediction request. Select the median prediction request time or 90th, 95th, or 99th percentile. |
| Median/Peak Load  | The median and maximum number of requests per minute. |
| Data Error Rate   | The percentage of requests that result in a 4xx error (problems with the prediction request submission). This is a component of the value reported as the Service Health Summary in the [**Deployments**](deploy-inventory) page top banner. |
| System Error Rate | The percentage of well-formed requests that result in a 5xx error (problem with the DataRobot prediction server). This is a component of the value reported as the Service Health Summary in the [**Deployments**](deploy-inventory) page top banner. |
| Consumers | The number of distinct users (identified by API key) who have made prediction requests against this deployment. |
| Cache Hit Rate | The percentage of requests that used a cached model (the model was recently used by other predictions). If not cached, DataRobot has to look the model up, which can cause delays. The prediction server cache holds 16 models by default, dropping the least-used dropped when the limit is reached. |

##  Understand the Service Health chart {: #understand-the-service-health-chart }

The chart below the tiled metrics displays individual metrics over time, helping to identify patterns in the quality of service. Clicking on a metric tile updates the chart to represent that information; you can also export it. Adjust the data range slider to narrow in on a specific period:

![](images/service-health-slider.png)

Some charts will display multiple metrics:

![](images/service-health-multi-metric.png)

## View MLOps Logs {: #view-mlops-logs }

On the MLOps Logs tab, you can view important deployment events. These events can help diagnose issues with a deployment or provide a record of the actions leading to the current state of the deployment. Each event has a type and a status. You can filter the event log by event type, event status, or time of occurrence, and you can view more details for an event on the Event Details panel.

1. On a deployment's **Service Health** page, scroll to the **Recent Activity** section at the bottom of the page.

2. In the **Recent Activity** section, click **MLOps Logs**.

3. Under **MLOps Logs**, configure any of the following filters:

    ![](images/mlops-logs-filter.png)

    | Element | Description |
    |---|---|
    | ![](images/icon-1.png) | Set the **Categories** filter to display log events by deployment feature: <ul><li>**Accuracy**: events related to actuals processing.</li><li>**Challengers**: events related to challengers functionality.</li><li>**Monitoring**: events related to general deployment actions; for example, model replacements or clearing deployment stats.</li><li>**Predictions**: events related to predictions processing.</li><li>**Retraining**: events related to deployment retraining functionality.</li></ul>The default filter displays all event categories. |
    | ![](images/icon-2.png) | Set the **Status Type** filter to display events by  status: <ul><li>**Success**</li><li>**Warning**</li><li>**Failure**</li><li>**Info**</li></ul> The default filter displays **Any** status type. |
    | ![](images/icon-3.png) | Set the **Range (UTC)** filter to display events logged within the specified range (UTC). The default filter displays the last seven days up to the current date and time. |

    ??? faq "What errors are surfaced in the MLOps Logs?"
        * Actuals with missing values
        * Actuals with duplicate association ID
        * Actuals with invalid payload
        * Challenger created
        * Challenger deleted
        * Challenger replay error
        * Challenger model validation error
        * Deployment historical stats reset
        * Model replacement validation warning
        * Prediction processing limit reached
        * Predictions missing required association ID
        * Retraining policy success
        * Retraining policy error

4. On the left panel, the **MLOps Logs** list displays deployment events with any selected filters applied. For each event, you can view a summary that includes the event name and status icon, the timestamp, and an event message preview.

5. Click the event you want to examine and review the **Event Details** panel on the right.

    ![](images/mlops-logs-details.png)

    === "General event details"

        This panel includes the following details:

        * Title
        * Status Type (with a success, warning, failure, or info label)
        * Timestamp
        * Message (with text describing the event)

    === "Event-specific details"

        You can also view the following details if applicable to the current event:

        * Model ID
        * Model Package ID (with a link to the package in the Model Registry if MLOps is enabled)
        * Catalog ID (with a link to the dataset in the AI Catalog)
        * Challenger ID
        * Prediction Job ID (for the related batch prediction job)
        * Affected Indexes (with a list of indexes related to the error event)
        * Start/End Date (for events covering a specified period; for example, resetting deployment stats)

    !!! tip
        For ID fields without a link, you can copy the ID by clicking the copy button ![](images/icon-copy.png).