Description
What: new feature allowing users to manage custom settings and mappings for a given integration namespace. The documentation page at https://www.elastic.co/docs/reference/fleet/data-streams should be updated to reflect this.
When: target feature 9.5.0, already available in serverless since 12 May 2026
Why: this allows users who manage multiple integrations under a shared namespace to managed common settings and mappings across all data streams in that namespace without configuring each data stream individually
Feature details
When this feature is enabled for a package namespace, Fleet-managed namespace index templates are created for each data stream defined by the package. They are named according to {type}-{dataset}@namespace.{namespace}, e.g. logs-system.application@namespace.production, and their composed_of contains a reference to a {namespace}@custom component template, which is left to the user to create. Cf. screenshots in elastic/kibana#269141 (and fixes from elastic/kibana#271465).
Resources
This feature was scoped and implemented in:
Possible enhancement (TBC): elastic/kibana#267291
Which deployment methods does this change impact?
Elastic On-Prem and Cloud (all)
Feature differences
No response
What Elastic Stack release is this request related to?
9.5
Serverless release
already available in serverless since 12 May 2026
Collaboration model
Unknown
Point of contact.
Main contact: @jillguyonnet
Stakeholders: @elastic/fleet
Elastic Docs AI Scoping 🤖
Docs issue scope
Summary
The issue asks for docs on a new Fleet feature: opt-in namespace-level index template customization, letting users apply a shared {namespace}@Custom component template across all data streams sharing a namespace (instead of customizing each data stream individually). Linked PRs [kibana#262568](https://github.com/elastic/kibana/pull/262568) (API), [kibana#269141](https://github.com/elastic/kibana/pull/269141) (UI), and [kibana#271465](https://github.com/elastic/kibana/pull/271465) (label fix) confirm this: Fleet creates a per-namespace index template named `{type}-{dataset}`@namespace`.{namespace}` (e.g. `logs-system.application@namespace.production`) with higher priority than the base template, composed with a user-created `{namespace}`@custom component template. Opt-in is per-package, configurable via API (namespace_customization_enabled_for, plus a new bulk endpoint) or via new UI: a Settings tab control on the integration and an Advanced options toggle ("Enable namespace-level customization") in the package policy editor.
Request accuracy
Accurate — confirmed against both merged PRs.
Next action for author
Add a new subsection to reference/fleet/data-streams.md under Index templates, documenting namespace-level @custom component templates alongside the existing type- and data-stream-level customization.
Impact: High
Scope boundary
No change needed to the sibling tutorial pages (data-streams-ilm-tutorial.md, data-streams-pipeline-tutorial.md, data-streams-advanced-features.md) — this feature is index-template customization at a new scope level, not ILM, ingest pipelines, or TSDS/synthetic source.
Recommended documentation targets
| Page |
URL |
Action |
Impact |
Confidence |
Why this page? |
| Data streams for Fleet |
reference/fleet/data-streams.md |
Add section to existing page |
High |
High |
Existing "Index templates" / "Edit the Elasticsearch index template" section already documents type-level (<type>@Custom) and data-stream-level (`<name_of_data_stream>`@custom) @custom component templates — namespace-level is the missing third tier and belongs directly alongside it. |
Recommendations
- In
reference/fleet/data-streams.md, add a new subsection under Index templates (after or within "Edit the Elasticsearch index template") explaining namespace-level customization: what it is, the {type}-{dataset}@namespace.{namespace} naming/priority scheme, that it's opt-in per package/namespace, and where to enable it in the UI (integration Settings tab, and package policy Advanced options toggle).
- Include the opt-in API examples from the PR description (
PUT /api/fleet/epm/packages/<pkg> with namespace_customization_enabled_for, and the bulk endpoint POST /api/fleet/epm/packages/_bulk_namespace_customization) as a brief code sample, consistent with the existing page's use of inline API snippets.
- Note the precedence order explicitly: data-stream-level
@custom still overrides namespace-level @custom, which overrides type-level @custom — this composed_of ordering (type@custom → namespace@custom → data-stream@custom) is a detail readers customizing multiple levels will need.
- Use
applies_to tagging for this subsection rather than the page-level stack: ga — the feature has been GA in Serverless since 2026-05-12 but targets Stack 9.5 (not yet released as of this analysis). Match the pattern already used elsewhere in reference/fleet/ for pre-GA stack features targeting 9.5, e.g. {applies_to}stack: ga 9.5+`` combined with serverless: ga (see `reference/fleet/fleet-enrollment-tokens.md` for a comparable inline usage).
Notes
- Page role fit:
data-streams.md is a mixed overview/how-to reference page already organized by index-template customization tier — adding a subsection keeps the section's existing pattern intact rather than introducing a new page for a narrower scope level of the same feature.
- No navigation, redirect, or cross-reference changes anticipated; this is additive content within an existing heading structure.
Generated by Issue Scope Analyzer for #6545 · sonnet 118.7 AIC · ⌖ 16.3 AIC · ⊞ 690 · ◷
Description
What: new feature allowing users to manage custom settings and mappings for a given integration namespace. The documentation page at https://www.elastic.co/docs/reference/fleet/data-streams should be updated to reflect this.
When: target feature 9.5.0, already available in serverless since 12 May 2026
Why: this allows users who manage multiple integrations under a shared namespace to managed common settings and mappings across all data streams in that namespace without configuring each data stream individually
Feature details
When this feature is enabled for a package namespace, Fleet-managed namespace index templates are created for each data stream defined by the package. They are named according to
{type}-{dataset}@namespace.{namespace}, e.g.logs-system.application@namespace.production, and theircomposed_ofcontains a reference to a{namespace}@customcomponent template, which is left to the user to create. Cf. screenshots in elastic/kibana#269141 (and fixes from elastic/kibana#271465).Resources
This feature was scoped and implemented in:
Possible enhancement (TBC): elastic/kibana#267291
Which deployment methods does this change impact?
Elastic On-Prem and Cloud (all)
Feature differences
No response
What Elastic Stack release is this request related to?
9.5
Serverless release
already available in serverless since 12 May 2026
Collaboration model
Unknown
Point of contact.
Main contact: @jillguyonnet
Stakeholders: @elastic/fleet
Elastic Docs AI Scoping 🤖
Docs issue scope
Summary
The issue asks for docs on a new Fleet feature: opt-in namespace-level index template customization, letting users apply a shared
{namespace}@Customcomponent template across all data streams sharing a namespace (instead of customizing each data stream individually). Linked PRs [kibana#262568](https://github.com/elastic/kibana/pull/262568) (API), [kibana#269141](https://github.com/elastic/kibana/pull/269141) (UI), and [kibana#271465](https://github.com/elastic/kibana/pull/271465) (label fix) confirm this: Fleet creates a per-namespace index template named `{type}-{dataset}`@namespace`.{namespace}` (e.g. `logs-system.application@namespace.production`) with higher priority than the base template, composed with a user-created `{namespace}`@customcomponent template. Opt-in is per-package, configurable via API (namespace_customization_enabled_for, plus a new bulk endpoint) or via new UI: a Settings tab control on the integration and an Advanced options toggle ("Enable namespace-level customization") in the package policy editor.Request accuracy
Accurate — confirmed against both merged PRs.
Next action for author
Add a new subsection to
reference/fleet/data-streams.mdunder Index templates, documenting namespace-level@customcomponent templates alongside the existing type- and data-stream-level customization.Impact: High
Scope boundary
No change needed to the sibling tutorial pages (
data-streams-ilm-tutorial.md,data-streams-pipeline-tutorial.md,data-streams-advanced-features.md) — this feature is index-template customization at a new scope level, not ILM, ingest pipelines, or TSDS/synthetic source.Recommended documentation targets
<type>@Custom) and data-stream-level (`<name_of_data_stream>`@custom)@customcomponent templates — namespace-level is the missing third tier and belongs directly alongside it.Recommendations
reference/fleet/data-streams.md, add a new subsection under Index templates (after or within "Edit the Elasticsearch index template") explaining namespace-level customization: what it is, the{type}-{dataset}@namespace.{namespace}naming/priority scheme, that it's opt-in per package/namespace, and where to enable it in the UI (integration Settings tab, and package policy Advanced options toggle).PUT /api/fleet/epm/packages/<pkg>withnamespace_customization_enabled_for, and the bulk endpointPOST /api/fleet/epm/packages/_bulk_namespace_customization) as a brief code sample, consistent with the existing page's use of inline API snippets.@customstill overrides namespace-level@custom, which overrides type-level@custom— this composed_of ordering (type@custom→namespace@custom→data-stream@custom) is a detail readers customizing multiple levels will need.applies_totagging for this subsection rather than the page-levelstack: ga— the feature has been GA in Serverless since 2026-05-12 but targets Stack 9.5 (not yet released as of this analysis). Match the pattern already used elsewhere inreference/fleet/for pre-GA stack features targeting 9.5, e.g.{applies_to}stack: ga 9.5+`` combined withserverless: ga(see `reference/fleet/fleet-enrollment-tokens.md` for a comparable inline usage).Notes
data-streams.mdis a mixed overview/how-to reference page already organized by index-template customization tier — adding a subsection keeps the section's existing pattern intact rather than introducing a new page for a narrower scope level of the same feature.