CPS: Data views automatically list indices from linked projects#5426
CPS: Data views automatically list indices from linked projects#5426florent-leborgne merged 8 commits intocps-tech-previewfrom
Conversation
Add a new section explaining that when CPS is active, the data view creation form automatically lists indices from linked projects based on the current CPS scope, with no opt-in required. Closes #687 Made-with: Cursor
✅ Vale Linting ResultsNo 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. |
Made-with: Cursor
…lified expressions - Index listing from linked projects only works from CPS-enabled apps (Discover, Dashboards, Lens, Maps), not from Stack Management - Add note about Stack Management limitation - Incorporate qualified expressions content (from MW's config PR) - Add link to search expressions reference Made-with: Cursor
Made-with: Cursor
|
Hey @mbondyra - I checked this against the instance that you provided. Let me know if that looks accurate to you or if there are things you'd change/clarify. Note: this will be merged to a feature branch first, that we'll promote on release day |
Made-with: Cursor
| stack: unavailable | ||
| ``` | ||
|
|
||
| When [{{cps}}](/explore-analyze/cross-project-search.md) is enabled and you have [linked projects](/explore-analyze/cross-project-search/cross-project-search-link-projects.md), the {{data-source}} creation form lists indices from linked projects based on the current [{{cps}} scope](/explore-analyze/cross-project-search/cross-project-search-manage-scope.md#cps-in-kibana). This applies when you create a {{data-source}} from within a {{cps}}-enabled app such as Discover, Dashboards, Lens, or Maps. The index list updates automatically when you change the {{cps}} scope. |
There was a problem hiding this comment.
optional: i'd maybe make it more clear that it's just a preview and the cps selection doesn't change what indices data view contains at the moment of creation. It is said here, but I feel like it still can be confusing.
There was a problem hiding this comment.
Ha very good point I'll make that clearer!
There was a problem hiding this comment.
Done in 39f8a1f - it was indeed not clear enough at all
| An index pattern like `logs-*` matches indices across the origin project and all linked projects in scope. | ||
|
|
||
| :::{note} | ||
| When you create a {{data-source}} from **Stack Management > Data Views**, the {{cps}} scope selector is not available and only indices from the current project are listed. |
There was a problem hiding this comment.
Actually, this is not accurate anymore - I was asked to add it (elastic/kibana#257801) - we can remove this section.
|
|
||
| To restrict a {{data-source}} to specific projects, you can: | ||
|
|
||
| * **Adjust the {{cps}} scope** in the {{cps-init}} scope selector before creating the {{data-source}}. |
There was a problem hiding this comment.
I think this is not accurate because what cps scope we have at the moment of creating data view doesn't matter, because it's just a preview, data view doesn't hold cps scope.
There was a problem hiding this comment.
Very good point, this should be fixed with 39f8a1f
- Clarify that the creation form shows a preview of indices based on the current CPS scope, but the data view itself does not store the scope - Remove outdated Stack Management note (CPS now supported there) - Remove misleading "adjust CPS scope" bullet (scope at creation time is only a preview) Made-with: Cursor
3 participants
Summary
Adds a "Use data sources with CPS" section to the data views page (
data-views.md), explaining how data views interact with cross-project search:project_alpha:logs-*,_origin:logs-*), or project routing in queries.Positioned after the existing CCS section as the serverless equivalent.
Closes elastic/docs-content-internal#687
Test plan
explore-analyze/find-and-organize/data-viewsapplies_totags render properly (serverless preview / stack unavailable)Generative AI disclosure
Tool(s) and model(s) used: Claude (Cursor)