Skip to content

[9.1] [Response Ops][Reporting] Store space_id in report doc generated from scheduled export (#225669)#226172

Merged
kibanamachine merged 1 commit intoelastic:9.1from
kibanamachine:backport/9.1/pr-225669
Jul 2, 2025
Merged

[9.1] [Response Ops][Reporting] Store space_id in report doc generated from scheduled export (#225669)#226172
kibanamachine merged 1 commit intoelastic:9.1from
kibanamachine:backport/9.1/pr-225669

Conversation

@kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 9.1:

Questions ?

Please refer to the Backport tool documentation

…om scheduled export (elastic#225669)

## Summary

Noticed during verification that the report document generated during
scheduled exports do not include the `space_id` field. We added it for
single exports in [this
PR](elastic#221375) but forgot to update
the scheduled export feature to pass through the space ID.

## To Verify

1. Create a scheduled export and wait for it to generate a report
2. Look for the doc in `.kibana-reporting`. It should contain the
`space_id` field.

Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
(cherry picked from commit d43d900)
@kibanamachine kibanamachine merged commit 5919e56 into elastic:9.1 Jul 2, 2025
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants