Skip to content

Document Synthetics multispace CCS settings - #7571

Open
alexandra5000 wants to merge 3 commits into
elastic:mainfrom
alexandra5000:docs/synthetics-multispace-settings
Open

Document Synthetics multispace CCS settings#7571
alexandra5000 wants to merge 3 commits into
elastic:mainfrom
alexandra5000:docs/synthetics-multispace-settings

Conversation

@alexandra5000

Copy link
Copy Markdown
Contributor

Summary

  • Adds a new Remote clusters section to the Synthetics settings page documenting the multispace CCS settings UI introduced in Kibana 9.5 (elastic/kibana#269250)
  • Adds a complementary section to the scale-and-architect page clarifying that the new native CCS integration (9.5+) is distinct from the CCS/CCR Kibana federation anti-pattern
  • Pre-existing style, applies_to, and frontmatter issues fixed across both files

Resolves: https://github.com/elastic/docs-content-internal/issues/1492

Generative AI disclosure

Did you use a generative AI (GenAI) tool to assist in creating this contribution?

  • Yes
  • No

If you answered Yes to the previous question, please specify the tool(s) and model(s) used (e.g., Google Gemini, OpenAI ChatGPT-4, etc.).
Tool(s) and model(s) used: Claude Opus 4.8

@github-actions

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

  • Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

@github-actions

github-actions Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented Jul 24, 2026

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

@alexandra5000
alexandra5000 marked this pull request as ready for review July 24, 2026 18:50
@alexandra5000
alexandra5000 requested a review from a team as a code owner July 24, 2026 18:50
Alerting enables you to detect complex conditions using **rules** across Observability and send a notification using **connectors**.

When you create a new synthetic monitor, new default synthetics rules will be applied. To edit the default rules:
When you create a new synthetic monitor, Synthetics applies new default rules to the monitor. To edit the default rules:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
When you create a new synthetic monitor, Synthetics applies new default rules to the monitor. To edit the default rules:
When you create a new synthetic monitor, Synthetics applies default rules to the monitor. To edit the default rules:

When you create a new synthetic monitor, Synthetics applies new default rules to the monitor. To edit the default rules:

1. Click **Alerts** in the top bar.
1. Click **Alerts** in the global header.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. Click **Alerts** in the global header.
1. Click **Alerts** in the application menu.

The global header is this

Image

See https://www.elastic.co/docs/contribute-docs/style-guide/ui-writing#naming-kibana-ui-elements

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh ok, thanks!

If you need specific alerting behavior, set up a different rule. To view all existing rules or create a new rule:

1. Click **Alerts** in the top bar.
1. Click **Alerts** in the global header.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
1. Click **Alerts** in the global header.
1. Click **Alerts** in the application menu.


There are several Synthetics settings you can adjust in Observability.

## Alerting [synthetics-settings-alerting]

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section is overall quite hard to read/understand and I think fails at explaining the core things clearly. It's not in the scope of your PR here, but I think it's worth creating an issue to rewrite at least the Alerting section, and/or see if it needs its own page.
If you update a rule, does the change apply to all monitors it's active on, or only new ones?
We say we can disable them for individual monitors but don't mention the option that controls it, etc.


## Remote clusters [synthetics-settings-remote-clusters]
```{applies_to}
stack: ga 9.5+

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
stack: ga 9.5+
stack: ga 9.5+
serverless: unavailable


In the **Remote clusters** tab, you can configure {{ccs}} ({{ccs-init}}) settings so that Synthetics can include monitor data from remote {{es}} clusters alongside your local monitors.

These settings apply to one or more {{kib}} spaces. Changes you make here affect all spaces that have access to these settings.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this sentence relates to the last subsection here but it's not super clear to me what it means. Is it: "You can apply these settings to other {{kib}} spaces." or "These settings only apply to the default space by default, but you can specify other spaces to share that configuration across them"? or something else.


### Spaces with access [synthetics-settings-remote-clusters-spaces]

Use the **Spaces** combo box to control which {{kib}} spaces these {{ccs-init}} settings apply to. You can select individual spaces, multiple spaces, or **All spaces** to share the settings across your entire deployment. Removing a space from the selection hides these settings in that space.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"individual spaces" (plural) / "multiple spaces" means the same thing. From what I see you either pick spaces individually, or select All spaces.

I'm not clear about the "removing..." part. Are the settings actually hidden (for me hidden means you can't configure it there anymore)? Or does that space just get to keep its own individual ccs configuration, not shared?


Use the **Spaces** combo box to control which {{kib}} spaces these {{ccs-init}} settings apply to. You can select individual spaces, multiple spaces, or **All spaces** to share the settings across your entire deployment. Removing a space from the selection hides these settings in that space.

If you leave the field empty, the current sharing configuration remains unchanged.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So we shouldn't even have the current space listed?

In complex environments, it’s common to have multiple task-specific {{stack}} deployments with one centralized overview cluster using {{ccs}} or {{ccr}} to centralize {{kib}} dashboards and apps. **Do not use this pattern with the Synthetics UI**. Instead, configure your synthetic monitors directly on the {{kib}} instance where you want to view and manage them.

You may, however, use Dashboards and the Discover feature with CCS to view `synthetics-*` indices.
You may, however, use the Dashboards and the Discover app with {{ccs-init}} to view `synthetics-*` indices.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
You may, however, use the Dashboards and the Discover app with {{ccs-init}} to view `synthetics-*` indices.
You may, however, use the Dashboards and the Discover apps with {{ccs-init}} to view `synthetics-*` indices.

Those are 2 different apps, if you want to keep the "app" word.

% Stateful only for do not use... section

## Do not use the Synthetics UI with CCS/CCR [synthetics-no-ccs-ccr]
## Do not use the Synthetics UI with {{ccs-init}}/{{ccr-init}} [synthetics-no-ccs-ccr]

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You added another section below but the difference is not made super clear. Maybe it would help to also add a reference to the actual integrated feature in here. Like "Do not use this pattern xxx, but instead use yyy". Or maybe combine these 2 into a single section that makes sense of the overall remote cluster + Synthetics story and recommendations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants