Skip to content

CPS in Kibana: global project picker, availability matrix, Transform & Vega#5423

Draft
florent-leborgne wants to merge 3 commits intocps-tech-previewfrom
cps/850-852-853-cps-in-kibana
Draft

CPS in Kibana: global project picker, availability matrix, Transform & Vega#5423
florent-leborgne wants to merge 3 commits intocps-tech-previewfrom
cps/850-852-853-cps-in-kibana

Conversation

@florent-leborgne
Copy link
Contributor

Summary

Adds foundational CPS documentation for Kibana apps:

  • New "CPS in Kibana" section on the CPS overview page (cross-project-search.md): explains the global project picker in the Kibana header, space default scope, and an availability matrix showing which Kibana apps support CPS and how (editable, read-only, or not available).
  • Transform limitation note (transforms.md): callout explaining CPS is not yet supported for transforms.
  • Vega CPS support note (custom-visualizations-with-vega.md): note that Vega is the only legacy visualization type supporting CPS.

Closes elastic/docs-content-internal#850
Closes elastic/docs-content-internal#852
Closes elastic/docs-content-internal#853

Test plan

  • Verify the availability matrix matches the current Kibana codebase CPS integration points
  • Verify the Transform callout wording matches the UI callout text
  • Check all cross-links resolve correctly
  • Confirm applies_to tags render properly for serverless preview / stack unavailable

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • Yes
  • No
  1. 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 (Cursor)

Made with Cursor

Add a new "CPS in Kibana" section to the cross-project search overview
page covering the global project picker, space default scope, and an
availability matrix for all Kibana apps. Also add a CPS limitation
callout to the Transforms page and a CPS support note to the Vega page.

Closes #850, closes #852, closes #853

Made-with: Cursor
@github-actions
Copy link
Contributor

github-actions bot commented Mar 10, 2026

Vale Linting Results

Summary: 2 warnings found

⚠️ Warnings (2)
File Line Rule Message
explore-analyze/transforms.md 18 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.
explore-analyze/visualize/custom-visualizations-with-vega.md 16 Elastic.QuotesPunctuation Place punctuation inside closing quotation marks.

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.

- Rewrite passive constructions to active voice across all three files
- Link Vega project routing mention to the CPS project routing page

Made-with: Cursor
Use the term "CPS scope selector" consistently, matching the UI popover
title "Cross-project search (CPS) scope". Introduce the full name on
first mention, then use the abbreviation throughout.

Made-with: Cursor
| **Maps** | Full (editable scope) | Change the {{cps}} scope. Vector layers and joins source data from linked projects based on the current scope. |
| **Visualize (Vega only)** | Full (editable scope) | {{cps}} is supported for [Vega visualizations](/explore-analyze/visualize/custom-visualizations-with-vega.md) only. Other legacy visualization types do not support {{cps}}. |
| **Security dashboards** | Full (editable scope) | {{cps}} is available on Security dashboard pages. Other Security solution pages do not support {{cps}}. |
| **{{rules-ui}} and alerts** | Read-only scope | The {{cps-init}} scope selector shows the current scope, but you cannot change it from this page. {{rules-ui}} use the space-level {{cps}} scope at execution time. |
Copy link
Contributor

Choose a reason for hiding this comment

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

@tiamliu @approksiu @yctercero users can you verify this change? I thought it's possible to specify project routing directly in rule queries and filters to target specific linked projects.

Suggested change
| **{{rules-ui}} and alerts** | Read-only scope | The {{cps-init}} scope selector shows the current scope, but you cannot change it from this page. {{rules-ui}} use the space-level {{cps}} scope at execution time. |
| **{{rules-ui}} and alerts** | Full (editable scope) | The {{cps-init}} scope selector shows the current scope, but you can change the {{cps}} scope when creating or editing rules. Otherwise, {{rules-ui}} use the space-level {{cps}} scope at execution time. |

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