From 14064698766dcd47c06f444ca0fe812f4f81cec1 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Wed, 26 Aug 2026 17:07:51 -0400 Subject: [PATCH 1/6] stub out cps support for synthetics --- .../create-monitor-status-rule.md | 5 ++ .../observability/synthetics/analyze-data.md | 67 +++++++++++++------ .../synthetics/configure-settings.md | 8 +++ .../synthetics/manage-monitors.md | 3 +- .../scale-architect-synthetics-deployment.md | 12 +++- 5 files changed, 71 insertions(+), 24 deletions(-) diff --git a/solutions/observability/incident-management/create-monitor-status-rule.md b/solutions/observability/incident-management/create-monitor-status-rule.md index 458c38d43c..b45e3b608f 100644 --- a/solutions/observability/incident-management/create-monitor-status-rule.md +++ b/solutions/observability/incident-management/create-monitor-status-rule.md @@ -30,6 +30,11 @@ To create synthetic monitor status rules, you need the following: This rule only queries against `synthetics-*` and that is hardcoded. +:::{note} +:applies_to: serverless: preview +This rule queries monitors in the origin project only. Monitors from linked projects in the Synthetics UI are not evaluated. +::: + ## Filters [observability-monitor-status-alert-filters] The **Filter by** section controls the scope of the rule. The rule will only check monitors that match the filters defined in this section. In this example, the rule will only alert on `browser` monitors located in `Asia/Pacific - Japan`. diff --git a/solutions/observability/synthetics/analyze-data.md b/solutions/observability/synthetics/analyze-data.md index 89a1d0c19a..8d9fb8b8b6 100644 --- a/solutions/observability/synthetics/analyze-data.md +++ b/solutions/observability/synthetics/analyze-data.md @@ -37,27 +37,6 @@ To get started with your analysis in the Overview tab, you can search for monito Then click an individual monitor to see some details in a flyout. From there, you can click **Go to monitor** to go to an individual monitor’s page to see more details (as described below). -## Remote monitors [synthetics-analyze-remote-monitors] -```{applies_to} -stack: ga 9.5+ -serverless: unavailable -``` - -When you configure {{ccs-init}} in [**{{synthetics-app}} → Settings → Remote clusters**](/solutions/observability/synthetics/configure-settings.md#synthetics-settings-remote-clusters), monitors from remote {{es}} clusters appear in the Synthetics UI alongside your local monitors. Remote monitors are identified by a **Remote** badge showing the cluster name, displayed next to the monitor type badge. - -When remote monitors are present, a **Remote cluster** filter option appears alongside **Type**, **Location**, **Tags**, and **Frequency**. Use it to scope the overview to monitors from one or more specific remote clusters. When a remote cluster filter is active, local monitors are hidden and status counts (for example, Up or Down) reflect only the filtered set. To group monitors by remote cluster, select **Group by → Remote cluster**. - -You can open a remote monitor's individual page the same way as a local monitor. Because remote monitors have no local saved object, the following actions are not available: - -- **Edit monitor** -- **Enable/Disable** -- **Delete** -- **Run test manually** - -:::{tip} -**Refresh** remains available. If you have monitors from multiple remote clusters, the **Remote** badge shows which {{kib}} instance each monitor comes from. To edit, enable/disable, delete, or run a remote monitor, open the Synthetics UI on the {{kib}} instance where the monitor is defined. -::: - ## All monitor types [synthetics-analyze-individual-monitors] When you go to an individual monitor’s page, you’ll see much more detail about the monitor’s performance over time. The details vary by monitor type, but for every monitor at the top of the page you’ll see: @@ -266,4 +245,48 @@ Without leaving the waterfall chart, you can view data points relating to each r For additional analysis, whether to check the content of a CSS file or to view a specific image, click the ![External link icon](/solutions/images/observability-popout.svg "") icon located beside each resource, to view its content in a new tab. -You can also navigate between steps and checks at the top of the page to view the corresponding waterfall charts. \ No newline at end of file +You can also navigate between steps and checks at the top of the page to view the corresponding waterfall charts. + +## Monitors from linked projects [synthetics-analyze-linked-monitors] +```{applies_to} +serverless: preview +stack: unavailable +``` + +When [{{cps}} ({{cps-init}})](/explore-analyze/cross-project-search.md) is enabled and projects are linked, the Synthetics **Overview**, monitor details, certificates, errors, and journeys pages use the [{{cps-init}} scope selector](/explore-analyze/cross-project-search/cross-project-search-manage-scope.md#cps-in-kibana) ({icon}`cross_project_search`) in the project header. Select **All projects** or a linked project to include monitor data from those projects. Scope also follows any [space default](/deploy-manage/cross-project-search-config/cps-config-access-and-scope.md#cps-default-search-scope). If your organization has only one project, the selector is hidden. + +Monitors from linked projects appear alongside monitors from the origin project and show a **Linked** badge next to the monitor type. When they are present, a **Linked project** filter appears alongside **Type**, **Location**, **Tags**, and **Frequency**. Use it to scope the overview to monitors from one or more linked projects. When that filter is active, monitors from the origin project are hidden and status counts reflect only the filtered set. To group monitors by linked project, select **Group by → Linked project**. + +You can open a monitor from a linked project the same way as a monitor from the origin project. The details page shows a **Linked project monitor** callout. Click **View on linked project** when the linked project's {{kib}} URL is available. Because these monitors have no local saved object, the following actions are not available: + +- **Edit monitor** +- **Enable/Disable** +- **Delete** +- **Run test manually** + +:::{tip} +**Refresh** remains available. The **Linked** badge shows which linked project each monitor comes from. To edit, enable/disable, delete, or run a monitor from a linked project, open the Synthetics UI on the project where the monitor is defined. +::: + +Creating, editing, and deleting monitors stays in the origin project. On **Create monitor**, **Edit monitor**, **Settings**, and **Management**, the scope selector is unavailable and Synthetics searches the origin project only. + +## Remote monitors [synthetics-analyze-remote-monitors] +```{applies_to} +stack: ga 9.5+ +serverless: unavailable +``` + +When you configure {{ccs-init}} in [**{{synthetics-app}} → Settings → Remote clusters**](/solutions/observability/synthetics/configure-settings.md#synthetics-settings-remote-clusters), monitors from remote {{es}} clusters appear in the Synthetics UI alongside your local monitors. Remote monitors are identified by a **Remote** badge showing the cluster name, displayed next to the monitor type badge. + +When remote monitors are present, a **Remote cluster** filter option appears alongside **Type**, **Location**, **Tags**, and **Frequency**. Use it to scope the overview to monitors from one or more specific remote clusters. When a remote cluster filter is active, local monitors are hidden and status counts (for example, Up or Down) reflect only the filtered set. To group monitors by remote cluster, select **Group by → Remote cluster**. + +You can open a remote monitor's individual page the same way as a local monitor. Because remote monitors have no local saved object, the following actions are not available: + +- **Edit monitor** +- **Enable/Disable** +- **Delete** +- **Run test manually** + +:::{tip} +**Refresh** remains available. If you have monitors from multiple remote clusters, the **Remote** badge shows which {{kib}} instance each monitor comes from. To edit, enable/disable, delete, or run a remote monitor, open the Synthetics UI on the {{kib}} instance where the monitor is defined. +::: \ No newline at end of file diff --git a/solutions/observability/synthetics/configure-settings.md b/solutions/observability/synthetics/configure-settings.md index 3d0c7b8f46..3db312a4e8 100644 --- a/solutions/observability/synthetics/configure-settings.md +++ b/solutions/observability/synthetics/configure-settings.md @@ -116,6 +116,14 @@ In a serverless project, to create a Project API key you must be logged in as a - The **Elastic managed locations enabled** toggle controls whether your Synthetics monitors are permitted to run from Elastic's globally distributed, cloud-hosted testing infrastructure. If enabled, the key can push monitors to both Elastic-managed and private locations. If disabled, the key is restricted to private locations only. - The **Spaces** menu allows you to select the space where your API keys are available. +## Cross-project search [synthetics-settings-cps] +```{applies_to} +serverless: preview +stack: unavailable +``` + +The **Remote clusters** tab is not available on {{serverless-full}}. To include monitors from linked projects, use the [{{cps-init}} scope selector](/explore-analyze/cross-project-search/cross-project-search-manage-scope.md#cps-in-kibana) ({icon}`cross_project_search`) in the project header. On this **Settings** page, the selector is unavailable and Synthetics stays scoped to the origin project. Refer to [Monitors from linked projects](/solutions/observability/synthetics/analyze-data.md#synthetics-analyze-linked-monitors). + ## Remote clusters [synthetics-settings-remote-clusters] ```{applies_to} stack: ga 9.5+ diff --git a/solutions/observability/synthetics/manage-monitors.md b/solutions/observability/synthetics/manage-monitors.md index f553538891..227a0f12a5 100644 --- a/solutions/observability/synthetics/manage-monitors.md +++ b/solutions/observability/synthetics/manage-monitors.md @@ -17,7 +17,8 @@ After you’ve [created a synthetic monitor](/solutions/observability/synthetics If you’re using {{project-monitors}}, you should also set up a workflow that uses [best practices for managing monitors effectively](/solutions/observability/synthetics/manage-monitors.md#synthetics-projects-best-practices) in a production environment. ::::{note} -Remote monitors (monitors loaded from remote {{es}} clusters using {{ccs}}) are read-only. **Edit**, **Enable/Disable**, **Delete**, and **Run test manually** actions are not available for them. To manage a remote monitor, use the {{synthetics-app}} on the {{kib}} instance where the monitor is defined. Refer to [Remote monitors](/solutions/observability/synthetics/analyze-data.md#synthetics-analyze-remote-monitors) for details. +* {applies_to}`stack: ga 9.5+` Remote monitors, loaded from remote {{es}} clusters using {{ccs}}, are read-only. **Edit**, **Enable/Disable**, **Delete**, and **Run test manually** actions are not available for them. To manage a remote monitor, use the {{synthetics-app}} on the {{kib}} instance where the monitor is defined. Refer to [Remote monitors](/solutions/observability/synthetics/analyze-data.md#synthetics-analyze-remote-monitors). +* {applies_to}`serverless: preview` Monitors from linked projects are read-only. **Edit**, **Enable/Disable**, **Delete**, and **Run test manually** actions are not available. On this page, the [{{cps-init}} scope selector](/explore-analyze/cross-project-search/cross-project-search-manage-scope.md#cps-in-kibana) is unavailable and Synthetics stays scoped to the origin project. To manage a monitor from a linked project, use the {{synthetics-app}} on the project where the monitor is defined. Refer to [Monitors from linked projects](/solutions/observability/synthetics/analyze-data.md#synthetics-analyze-linked-monitors). :::: ## Update a monitor [manage-monitors-config] diff --git a/solutions/observability/synthetics/scale-architect-synthetics-deployment.md b/solutions/observability/synthetics/scale-architect-synthetics-deployment.md index 54c8419f9d..8ba8c6d7c7 100644 --- a/solutions/observability/synthetics/scale-architect-synthetics-deployment.md +++ b/solutions/observability/synthetics/scale-architect-synthetics-deployment.md @@ -9,13 +9,23 @@ applies_to: products: - id: observability - id: cloud-serverless -description: Advanced guidance for scaling and designing Elastic Synthetics deployments, including cross-cluster search support, tagging strategies, and custom dashboards. +description: Advanced guidance for scaling and designing Elastic Synthetics deployments, including cross-project and cross-cluster search support, tagging strategies, and custom dashboards. --- # Scale and architect a Synthetics deployment [synthetics-scale-and-architect] Use these advanced considerations when you use the {{synthetics-app}} for large and complex use cases. +## View monitor data from linked projects [synthetics-cps-settings] +```{applies_to} +serverless: preview +stack: unavailable +``` + +On {{serverless-full}}, include monitors from linked projects with the [{{cps-init}} scope selector](/explore-analyze/cross-project-search/cross-project-search-manage-scope.md#cps-in-kibana) ({icon}`cross_project_search`) in the project header. + +Monitors from linked projects are read-only in this project. Create, edit, and delete them in the project where they are defined. Refer to [Monitors from linked projects](/solutions/observability/synthetics/analyze-data.md#synthetics-analyze-linked-monitors). + ## View monitor data from remote clusters [synthetics-ccs-settings] ```{applies_to} stack: ga 9.5+ From 59c82c17de59d972343bdedddfb9d58d816241f0 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Thu, 27 Aug 2026 14:17:27 -0400 Subject: [PATCH 2/6] some edits --- solutions/observability/synthetics/analyze-data.md | 4 ++-- solutions/observability/synthetics/manage-monitors.md | 8 ++++++-- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/solutions/observability/synthetics/analyze-data.md b/solutions/observability/synthetics/analyze-data.md index 8d9fb8b8b6..226674c798 100644 --- a/solutions/observability/synthetics/analyze-data.md +++ b/solutions/observability/synthetics/analyze-data.md @@ -13,7 +13,7 @@ products: # Analyze data from synthetic monitors -The Synthetics UI gives you a high-level overview of your service’s availability and allows you to dig into details to diagnose what caused downtime. +The Synthetics UI gives you a high-level overview of your service’s availability and allows you to dig into details to diagnose what caused downtime. You can view monitor data from the current cluster or {{serverless-short}} project, as well as from [remote clusters](/solutions/observability/synthetics/analyze-data.md#synthetics-analyze-remote-monitors) or [linked projects](/solutions/observability/synthetics/analyze-data.md#synthetics-analyze-linked-monitors). ## Overview [synthetics-analyze-overview] @@ -253,7 +253,7 @@ serverless: preview stack: unavailable ``` -When [{{cps}} ({{cps-init}})](/explore-analyze/cross-project-search.md) is enabled and projects are linked, the Synthetics **Overview**, monitor details, certificates, errors, and journeys pages use the [{{cps-init}} scope selector](/explore-analyze/cross-project-search/cross-project-search-manage-scope.md#cps-in-kibana) ({icon}`cross_project_search`) in the project header. Select **All projects** or a linked project to include monitor data from those projects. Scope also follows any [space default](/deploy-manage/cross-project-search-config/cps-config-access-and-scope.md#cps-default-search-scope). If your organization has only one project, the selector is hidden. +When [projects are linked](/deploy-manage/cross-project-search-config/cps-config-link-and-manage.md), the Synthetics **Overview**, monitor details, certificates, errors, and journeys pages use the [{{cps-init}} scope selector](/explore-analyze/cross-project-search/cross-project-search-manage-scope.md#cps-in-kibana) ({icon}`cross_project_search`) in the project header. Select **All projects** or a linked project to include monitor data from those projects. Scope also follows any [space default](/deploy-manage/cross-project-search-config/cps-config-access-and-scope.md#cps-default-search-scope). Monitors from linked projects appear alongside monitors from the origin project and show a **Linked** badge next to the monitor type. When they are present, a **Linked project** filter appears alongside **Type**, **Location**, **Tags**, and **Frequency**. Use it to scope the overview to monitors from one or more linked projects. When that filter is active, monitors from the origin project are hidden and status counts reflect only the filtered set. To group monitors by linked project, select **Group by → Linked project**. diff --git a/solutions/observability/synthetics/manage-monitors.md b/solutions/observability/synthetics/manage-monitors.md index 227a0f12a5..045ec95e3a 100644 --- a/solutions/observability/synthetics/manage-monitors.md +++ b/solutions/observability/synthetics/manage-monitors.md @@ -17,8 +17,12 @@ After you’ve [created a synthetic monitor](/solutions/observability/synthetics If you’re using {{project-monitors}}, you should also set up a workflow that uses [best practices for managing monitors effectively](/solutions/observability/synthetics/manage-monitors.md#synthetics-projects-best-practices) in a production environment. ::::{note} -* {applies_to}`stack: ga 9.5+` Remote monitors, loaded from remote {{es}} clusters using {{ccs}}, are read-only. **Edit**, **Enable/Disable**, **Delete**, and **Run test manually** actions are not available for them. To manage a remote monitor, use the {{synthetics-app}} on the {{kib}} instance where the monitor is defined. Refer to [Remote monitors](/solutions/observability/synthetics/analyze-data.md#synthetics-analyze-remote-monitors). -* {applies_to}`serverless: preview` Monitors from linked projects are read-only. **Edit**, **Enable/Disable**, **Delete**, and **Run test manually** actions are not available. On this page, the [{{cps-init}} scope selector](/explore-analyze/cross-project-search/cross-project-search-manage-scope.md#cps-in-kibana) is unavailable and Synthetics stays scoped to the origin project. To manage a monitor from a linked project, use the {{synthetics-app}} on the project where the monitor is defined. Refer to [Monitors from linked projects](/solutions/observability/synthetics/analyze-data.md#synthetics-analyze-linked-monitors). +This page lists only monitors defined in the current cluster or {{serverless-short}} project. To change a monitor that isn't listed, open the Synthetics UI on the cluster or project where the monitor is defined. + +For more information, refer to the following topics: + +* {applies_to}`stack: ga 9.5+` [Remote monitors](/solutions/observability/synthetics/analyze-data.md#synthetics-analyze-remote-monitors). +* {applies_to}`serverless: preview` [Monitors from linked projects](/solutions/observability/synthetics/analyze-data.md#synthetics-analyze-linked-monitors). :::: ## Update a monitor [manage-monitors-config] From 0099b24227e16c7bcb66b80d33d8483be97d4ad9 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Thu, 27 Aug 2026 14:25:46 -0400 Subject: [PATCH 3/6] edit --- solutions/observability/synthetics/analyze-data.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solutions/observability/synthetics/analyze-data.md b/solutions/observability/synthetics/analyze-data.md index 226674c798..587851344d 100644 --- a/solutions/observability/synthetics/analyze-data.md +++ b/solutions/observability/synthetics/analyze-data.md @@ -253,7 +253,7 @@ serverless: preview stack: unavailable ``` -When [projects are linked](/deploy-manage/cross-project-search-config/cps-config-link-and-manage.md), the Synthetics **Overview**, monitor details, certificates, errors, and journeys pages use the [{{cps-init}} scope selector](/explore-analyze/cross-project-search/cross-project-search-manage-scope.md#cps-in-kibana) ({icon}`cross_project_search`) in the project header. Select **All projects** or a linked project to include monitor data from those projects. Scope also follows any [space default](/deploy-manage/cross-project-search-config/cps-config-access-and-scope.md#cps-default-search-scope). +When [projects are linked](/deploy-manage/cross-project-search-config/cps-config-link-and-manage.md), the Synthetics **Overview**, monitor details, certificates, errors, and journeys pages use the [{{cps-init}} scope selector](/explore-analyze/cross-project-search/cross-project-search-manage-scope.md#cps-in-kibana) ({icon}`cross_project_search`) in the project header. Select **All projects** or a linked project to include monitor data from those projects. Monitors from linked projects appear alongside monitors from the origin project and show a **Linked** badge next to the monitor type. When they are present, a **Linked project** filter appears alongside **Type**, **Location**, **Tags**, and **Frequency**. Use it to scope the overview to monitors from one or more linked projects. When that filter is active, monitors from the origin project are hidden and status counts reflect only the filtered set. To group monitors by linked project, select **Group by → Linked project**. From 7953db9dbb4f989c2f4d5176a8b712ef3bb1a068 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Thu, 27 Aug 2026 15:51:49 -0400 Subject: [PATCH 4/6] tighter --- .../observability/synthetics/configure-settings.md | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/solutions/observability/synthetics/configure-settings.md b/solutions/observability/synthetics/configure-settings.md index 3db312a4e8..719d3342fc 100644 --- a/solutions/observability/synthetics/configure-settings.md +++ b/solutions/observability/synthetics/configure-settings.md @@ -116,14 +116,6 @@ In a serverless project, to create a Project API key you must be logged in as a - The **Elastic managed locations enabled** toggle controls whether your Synthetics monitors are permitted to run from Elastic's globally distributed, cloud-hosted testing infrastructure. If enabled, the key can push monitors to both Elastic-managed and private locations. If disabled, the key is restricted to private locations only. - The **Spaces** menu allows you to select the space where your API keys are available. -## Cross-project search [synthetics-settings-cps] -```{applies_to} -serverless: preview -stack: unavailable -``` - -The **Remote clusters** tab is not available on {{serverless-full}}. To include monitors from linked projects, use the [{{cps-init}} scope selector](/explore-analyze/cross-project-search/cross-project-search-manage-scope.md#cps-in-kibana) ({icon}`cross_project_search`) in the project header. On this **Settings** page, the selector is unavailable and Synthetics stays scoped to the origin project. Refer to [Monitors from linked projects](/solutions/observability/synthetics/analyze-data.md#synthetics-analyze-linked-monitors). - ## Remote clusters [synthetics-settings-remote-clusters] ```{applies_to} stack: ga 9.5+ @@ -138,6 +130,11 @@ These settings are stored as a single shared configuration — one per deploymen To edit these settings, you must have the **All** privilege for the **Synthetics and Uptime** feature in **{{stack-manage-app}} → Roles → {{kib}} privileges → {{observability}}**. Users with only the **Read** privilege see the form as read-only. :::: +::::{admonition} View monitors from linked projects +:applies_to: serverless: preview +On {{serverless-full}}, after you [link projects](/deploy-manage/cross-project-search-config/cps-config-link-and-manage.md), you can view monitors from those projects without any additional configuration. Refer to [Monitors from linked projects](/solutions/observability/synthetics/analyze-data.md#synthetics-analyze-linked-monitors). +:::: + ### Source settings [synthetics-settings-remote-clusters-source] Use the **Use all remote clusters** toggle or **Select remote clusters** combo box to control which remote clusters Synthetics queries: From 1c9fd0e65bfde1fa08c15ffcd74a57e718c3d09f Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Thu, 27 Aug 2026 16:46:36 -0400 Subject: [PATCH 5/6] parallelism --- .../synthetics/scale-architect-synthetics-deployment.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/solutions/observability/synthetics/scale-architect-synthetics-deployment.md b/solutions/observability/synthetics/scale-architect-synthetics-deployment.md index 8ba8c6d7c7..ddc4c49703 100644 --- a/solutions/observability/synthetics/scale-architect-synthetics-deployment.md +++ b/solutions/observability/synthetics/scale-architect-synthetics-deployment.md @@ -22,9 +22,11 @@ serverless: preview stack: unavailable ``` -On {{serverless-full}}, include monitors from linked projects with the [{{cps-init}} scope selector](/explore-analyze/cross-project-search/cross-project-search-manage-scope.md#cps-in-kibana) ({icon}`cross_project_search`) in the project header. +On {{serverless-full}}, you can view monitor data from linked projects alongside monitors from the origin project, directly in the Synthetics UI. -Monitors from linked projects are read-only in this project. Create, edit, and delete them in the project where they are defined. Refer to [Monitors from linked projects](/solutions/observability/synthetics/analyze-data.md#synthetics-analyze-linked-monitors). +This view is read-only, meaning Synthetics builds it from monitor check data when you load the page. Monitor definitions stay as saved objects on the project where they were created. To create, edit, or delete those monitors, manage them directly in the Synthetics UI on that project. + +To include these monitors, [link projects](/deploy-manage/cross-project-search-config/cps-config-link-and-manage.md). Refer to [Monitors from linked projects](/solutions/observability/synthetics/analyze-data.md#synthetics-analyze-linked-monitors) for details. ## View monitor data from remote clusters [synthetics-ccs-settings] ```{applies_to} From 8d91f054401d4cb5524f40bdadca6035ad73c82d Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Thu, 27 Aug 2026 16:47:28 -0400 Subject: [PATCH 6/6] remove from irrelevant surface --- .../incident-management/create-monitor-status-rule.md | 5 ----- 1 file changed, 5 deletions(-) diff --git a/solutions/observability/incident-management/create-monitor-status-rule.md b/solutions/observability/incident-management/create-monitor-status-rule.md index b45e3b608f..458c38d43c 100644 --- a/solutions/observability/incident-management/create-monitor-status-rule.md +++ b/solutions/observability/incident-management/create-monitor-status-rule.md @@ -30,11 +30,6 @@ To create synthetic monitor status rules, you need the following: This rule only queries against `synthetics-*` and that is hardcoded. -:::{note} -:applies_to: serverless: preview -This rule queries monitors in the origin project only. Monitors from linked projects in the Synthetics UI are not evaluated. -::: - ## Filters [observability-monitor-status-alert-filters] The **Filter by** section controls the scope of the rule. The rule will only check monitors that match the filters defined in this section. In this example, the rule will only alert on `browser` monitors located in `Asia/Pacific - Japan`.