--- title: Journey Status description: Understand how Datadog determines the status of a journey. breadcrumbs: Docs > Journey Monitoring > Journey Status --- > For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt). # Journey Status {% callout %} # Important note for users on the following Datadog sites: app.ddog-gov.com, us2.ddog-gov.com {% alert level="danger" %} This product is not supported for your selected [Datadog site](https://docs.datadoghq.com/getting_started/site.md). ({% placeholder "user-datadog-site-name" /%}). {% /alert %} {% /callout %} ## Overview{% #overview %} Journey status summarizes a journey's technical health as **Healthy**, **Degraded**, or **Missing coverage**. Datadog calculates the status from two types of [service level objective (SLO)](https://docs.datadoghq.com/service_level_objectives.md) inputs: - SLOs on [Real User Monitoring (RUM) operations](https://docs.datadoghq.com/real_user_monitoring/operations_monitoring.md) linked to the journey - The [uptime SLO](https://docs.datadoghq.com/synthetics/test_suites.md#service-level-objectives) for the journey's [Synthetic test suite](https://docs.datadoghq.com/journey_monitoring/details_report.md#synthetic-monitoring--testing) Journey status reflects the latest state of these inputs. It does not provide status history or define a separate objective or evaluation window. {% image source="https://docs.dd-static.net/images/journey_monitoring/journey-monitoring-status.6f006792e70afcb30195b3bd3b5b121b.png?auto=format&fit=max&w=850 1x, https://docs.dd-static.net/images/journey_monitoring/journey-monitoring-status.6f006792e70afcb30195b3bd3b5b121b.png?auto=format&fit=max&w=850&dpr=2 2x" alt="Journey overview showing a degraded status caused by failing tests and a high test suite burn rate." /%} ## Status inputs{% #status-inputs %} Datadog evaluates the [burn rate](https://docs.datadoghq.com/service_level_objectives.md#slo-burn-rate-indicator) of each SLO input: - **High burn**: The SLO consumes its error budget faster than its target allows and is in or approaching breach. - **Low burn or OK**: The SLO consumes its error budget at an acceptable rate. - **No Data**: Datadog excludes the SLO from the calculation. Journey status does not require both input types. A single high-burn SLO from either type makes the journey **Degraded**. ### RUM operation SLOs{% #rum-operation-slos %} {% alert level="info" %} Creating RUM operations requires an active trial or paid subscription to [RUM without Limits™](https://docs.datadoghq.com/real_user_monitoring/rum_without_limits.md). After you link an operation to a journey, its SLOs can contribute to journey status. {% /alert %} The RUM operation input has a high burn rate when at least one SLO on a linked operation has a high burn rate. It is healthy when at least one operation SLO is included and every included SLO has a low burn rate or is OK. A linked RUM operation is explicitly identified as part of the journey's critical path. Linking distinguishes operations that users encounter during the journey from unrelated operations that run at the same time. Datadog excludes unlinked operations and linked operations without an SLO from the status calculation. When you link an operation without an SLO, Datadog creates an availability SLO with a 99% objective. Customize this SLO or add more availability and latency SLOs as needed. For guidance, see [Best Practices for Creating SLOs for RUM Operations](https://docs.datadoghq.com/real_user_monitoring/guide/best-practices-for-creating-slos-on-operations.md). Manage links from the operation details report, the journey [details report](https://docs.datadoghq.com/journey_monitoring/details_report.md), or the [RUM Operations API](https://docs.datadoghq.com/api/latest/rum-operations.md). ### Test suite uptime SLO{% #test-suite-uptime-slo %} {% alert level="info" %} Creating or managing the test suite and tests that provide this status input requires an active trial or paid subscription to [Synthetic Browser Tests](https://docs.datadoghq.com/synthetics/browser_tests.md) or [Synthetic Mobile Tests](https://docs.datadoghq.com/synthetics/mobile_app_testing.md). {% /alert %} The test suite has a time-slice uptime SLO that evaluates its critical tests. Tests are critical by default. Mark a test as non-critical to exclude it from the uptime SLO while keeping it in the suite. The test suite input has a high burn rate when its uptime SLO has a high burn rate. It is healthy when the uptime SLO has a low burn rate or is OK. If the suite has no test data, Datadog excludes this input from the calculation. ## Status calculation{% #status-calculation %} Datadog combines the included RUM operation and test suite inputs: - **Degraded**: At least one included SLO has a high burn rate - **Healthy**: At least one SLO is included, and every included SLO has a low burn rate or is OK - **Missing coverage**: No SLO input remains in the calculation. This occurs when the journey has no configured inputs or when all configured inputs report **No Data** Changes to the journey's inputs affect its status automatically. This includes linking RUM operations and adding or removing tests from the test suite. ## Investigate journey status{% #investigate-journey-status %} View journey status in the [catalog](https://docs.datadoghq.com/journey_monitoring/overview.md#journey-catalog), [map](https://docs.datadoghq.com/journey_monitoring/map.md), and details report: - For a **Degraded** journey, Datadog links to the **Critical** operations or the Synthetic tests in the **Alert** state that contribute to the status. If Bits AI is enabled for your organization, launch a [Bits Investigation](https://docs.datadoghq.com/bits_ai/bits_investigation.md) from the operation or test to identify the root cause. - For a journey with **Missing coverage**, [link an operation with an SLO](https://docs.datadoghq.com/journey_monitoring/configuring_journeys.md#review-matching-operations) or [add a covering test](https://docs.datadoghq.com/journey_monitoring/configuring_journeys.md#manage-tests). If coverage is configured, confirm that its SLO inputs report data. ## Further reading{% #further-reading %} Additional helpful documentation, links, and articles: - [Learn about Journey Monitoring](https://docs.datadoghq.com/journey_monitoring.md) - [Learn about RUM Operations Monitoring](https://docs.datadoghq.com/real_user_monitoring/operations_monitoring.md) - [Learn about Synthetic test coverage](https://docs.datadoghq.com/journey_monitoring/details_report.md#synthetic-monitoring--testing)