[Response Ops][Reporting] Store space_id in report doc generated from scheduled export#225669
Merged
ymao1 merged 5 commits intoelastic:mainfrom Jul 2, 2025
Merged
[Response Ops][Reporting] Store space_id in report doc generated from scheduled export#225669ymao1 merged 5 commits intoelastic:mainfrom
space_id in report doc generated from scheduled export#225669ymao1 merged 5 commits intoelastic:mainfrom
Conversation
ymao1
added
bug
Contributor
|
Pinging @elastic/response-ops (Team:ResponseOps) |
Contributor
Author
|
@elasticmachine merge upstream |
Contributor
Author
|
@elasticmachine merge upstream |
Contributor
Author
|
@elasticmachine merge upstream |
Contributor
💚 Build Succeeded
Metrics [docs]
History
cc @ymao1 |
pmuellr
approved these changes
Jul 2, 2025
Contributor
pmuellr
left a comment
pmuellr
left a comment
There was a problem hiding this comment.
LGTM; tested in a non-default space, noticed the space_id in the reporting docs, task manager docs, etc. Scheduled a report in a non-default space that worked.
Contributor
|
Starting backport for target branches: 8.19, 9.1 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jul 2, 2025
…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
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jul 2, 2025
…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)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Jul 2, 2025
…ated from scheduled export (#225669) (#226171) # Backport This will backport the following commits from `main` to `8.19`: - [[Response Ops][Reporting] Store `space_id` in report doc generated from scheduled export (#225669)](#225669) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ying Mao","email":"ying.mao@elastic.co"},"sourceCommit":{"committedDate":"2025-07-02T11:33:53Z","message":"[Response Ops][Reporting] Store `space_id` in report doc generated from scheduled export (#225669)\n\n## Summary\n\nNoticed during verification that the report document generated during\nscheduled exports do not include the `space_id` field. We added it for\nsingle exports in [this\nPR](#221375) but forgot to update\nthe scheduled export feature to pass through the space ID.\n\n## To Verify\n\n1. Create a scheduled export and wait for it to generate a report\n2. Look for the doc in `.kibana-reporting`. It should contain the\n`space_id` field.\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d43d90094aa2c6902624ccccd1c199f73fbfe9de","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","Feature:Reporting:Framework","backport:version","v9.1.0","v8.19.0","v9.2.0"],"title":"[Response Ops][Reporting] Store `space_id` in report doc generated from scheduled export","number":225669,"url":"https://github.com/elastic/kibana/pull/225669","mergeCommit":{"message":"[Response Ops][Reporting] Store `space_id` in report doc generated from scheduled export (#225669)\n\n## Summary\n\nNoticed during verification that the report document generated during\nscheduled exports do not include the `space_id` field. We added it for\nsingle exports in [this\nPR](#221375) but forgot to update\nthe scheduled export feature to pass through the space ID.\n\n## To Verify\n\n1. Create a scheduled export and wait for it to generate a report\n2. Look for the doc in `.kibana-reporting`. It should contain the\n`space_id` field.\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d43d90094aa2c6902624ccccd1c199f73fbfe9de"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.19"],"targetPullRequestStates":[{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/225669","number":225669,"mergeCommit":{"message":"[Response Ops][Reporting] Store `space_id` in report doc generated from scheduled export (#225669)\n\n## Summary\n\nNoticed during verification that the report document generated during\nscheduled exports do not include the `space_id` field. We added it for\nsingle exports in [this\nPR](#221375) but forgot to update\nthe scheduled export feature to pass through the space ID.\n\n## To Verify\n\n1. Create a scheduled export and wait for it to generate a report\n2. Look for the doc in `.kibana-reporting`. It should contain the\n`space_id` field.\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d43d90094aa2c6902624ccccd1c199f73fbfe9de"}}]}] BACKPORT--> Co-authored-by: Ying Mao <ying.mao@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
kibanamachine
added a commit
that referenced
this pull request
Jul 2, 2025
…ted from scheduled export (#225669) (#226172) # Backport This will backport the following commits from `main` to `9.1`: - [[Response Ops][Reporting] Store `space_id` in report doc generated from scheduled export (#225669)](#225669) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ying Mao","email":"ying.mao@elastic.co"},"sourceCommit":{"committedDate":"2025-07-02T11:33:53Z","message":"[Response Ops][Reporting] Store `space_id` in report doc generated from scheduled export (#225669)\n\n## Summary\n\nNoticed during verification that the report document generated during\nscheduled exports do not include the `space_id` field. We added it for\nsingle exports in [this\nPR](#221375) but forgot to update\nthe scheduled export feature to pass through the space ID.\n\n## To Verify\n\n1. Create a scheduled export and wait for it to generate a report\n2. Look for the doc in `.kibana-reporting`. It should contain the\n`space_id` field.\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d43d90094aa2c6902624ccccd1c199f73fbfe9de","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","Feature:Reporting:Framework","backport:version","v9.1.0","v8.19.0","v9.2.0"],"title":"[Response Ops][Reporting] Store `space_id` in report doc generated from scheduled export","number":225669,"url":"https://github.com/elastic/kibana/pull/225669","mergeCommit":{"message":"[Response Ops][Reporting] Store `space_id` in report doc generated from scheduled export (#225669)\n\n## Summary\n\nNoticed during verification that the report document generated during\nscheduled exports do not include the `space_id` field. We added it for\nsingle exports in [this\nPR](#221375) but forgot to update\nthe scheduled export feature to pass through the space ID.\n\n## To Verify\n\n1. Create a scheduled export and wait for it to generate a report\n2. Look for the doc in `.kibana-reporting`. It should contain the\n`space_id` field.\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d43d90094aa2c6902624ccccd1c199f73fbfe9de"}},"sourceBranch":"main","suggestedTargetBranches":["9.1","8.19"],"targetPullRequestStates":[{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/225669","number":225669,"mergeCommit":{"message":"[Response Ops][Reporting] Store `space_id` in report doc generated from scheduled export (#225669)\n\n## Summary\n\nNoticed during verification that the report document generated during\nscheduled exports do not include the `space_id` field. We added it for\nsingle exports in [this\nPR](#221375) but forgot to update\nthe scheduled export feature to pass through the space ID.\n\n## To Verify\n\n1. Create a scheduled export and wait for it to generate a report\n2. Look for the doc in `.kibana-reporting`. It should contain the\n`space_id` field.\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d43d90094aa2c6902624ccccd1c199f73fbfe9de"}}]}] BACKPORT--> Co-authored-by: Ying Mao <ying.mao@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
kertal
pushed a commit
to kertal/kibana
that referenced
this pull request
Jul 25, 2025
…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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Noticed during verification that the report document generated during scheduled exports do not include the
space_idfield. We added it for single exports in this PR but forgot to update the scheduled export feature to pass through the space ID.To Verify
.kibana-reporting. It should contain thespace_idfield.