Skip to content

[8.19] Adding space_id field mapping to kibana reporting template (#128336)#129061

Merged
elasticsearchmachine merged 1 commit intoelastic:8.19from
ymao1:backport/8.19/pr-128336
Jun 6, 2025
Merged

[8.19] Adding space_id field mapping to kibana reporting template (#128336)#129061
elasticsearchmachine merged 1 commit intoelastic:8.19from
ymao1:backport/8.19/pr-128336

Conversation

@ymao1
Copy link
Contributor

@ymao1 ymao1 commented Jun 6, 2025

Backports the following commits to 8.19:

…#128336)

* Adding space id to report template

* Incrementing stack template registry version
@ymao1 ymao1 added :StorageEngine/Data streams Data streams and their lifecycles >non-issue auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport Team:Data Management (obsolete) DO NOT USE. This team no longer exists. labels Jun 6, 2025
@elasticsearchmachine elasticsearchmachine merged commit b82d55a into elastic:8.19 Jun 6, 2025
15 checks passed
@ymao1 ymao1 deleted the backport/8.19/pr-128336 branch June 6, 2025 14:52
pmuellr added a commit to pmuellr/kibana that referenced this pull request Aug 8, 2025
… startup

resolves: elastic#231200

This PR adds code run at startup to:

- read the `.kibana-reporting` index template to get the mappings
- apply those mappings directly to the write index of the `.kibana-reporting` data stream

This is needed for those times when the mappings change, for instance in this PR: elastic/elasticsearch#129061.  The mappings do get updated, but are not applied to the data stream, so in fact the "new" fields (when updates happen) are not actually mapped in the existing data stream.

I was hoping to actually roll over the index, but it's not clear how we could determine if we need to, and we certainly don't want to do that on every restart.  Re-applying the mappings will ensure that any changes to the index template's mapping are made to the current index.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport >non-issue :StorageEngine/Data streams Data streams and their lifecycles Team:Data Management (obsolete) DO NOT USE. This team no longer exists. v8.19.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants