[Response Ops][Reporting] Scheduled Reports #221028

ymao1 · 2025-05-20T16:04:18Z

Summary

This is a feature branch that contains the following commits. Each individual linked PR contains a summary and verification instructions.

Schedule API - [Response Ops][Reporting] Scheduled Reports - Schedule API #219771
Scheduled report task runner - [Response Ops][Reporting] Scheduled Reports - Task (merging into feature branch) #219770
List and disable API - [Response Ops][Reporting] Scheduled Reports - List and Disable API #220922
Audit logging - [Response Ops][Reporting] Scheduled Reports - Audit Logging (merging into feature branch) #221846
Send scheduled report emails - [ResponseOps][Reporting] Send email with report attachment for scheduled reporting task (merging into feature branch) #220539
Commit to check license - f5f9d9d
Update to list API response format - [Response Ops][Reports] Updating list scheduled report API response #224262

Towards #216313 > [!Note] > This PR will be merged into a feature branch - `elastic:scheduled-reports` > Once this is merged, I will open a draft PR from the feature branch into `main` ## Summary ### Schedule API - Added internal API `/internal/reporting/schedule/{exportTypeId}` ``` POST /internal/reporting/schedule/{exportTypeId} { "jobParams": <same jobParams format as existing generate single report API>, "schedule": { "rrule": <modified Task Manager rRule schema from #217728> } "notification": { "email": { "to": <optional list of email addresses>, "cc": <optional list of email addresses>, "bcc": <optional list of email addresses> } } ``` - Scheduling a report creates a new `scheduled_report` type saved object in the `.kibana-alerting-cases` index. - Uses the same role privileges as the current generate report API, so user must have the reporting subfeature privilege for one of the Analytics feature privileges (Discover/Dashboard/Visualize) ## Verify 1. Run ES and Kibana with examples and install the sample web logs data set. 2. In the DEV console, call the schedule API using ``` POST kbn:/internal/reporting/schedule/printablePdfV2 { "schedule": { "rrule": { "freq": 3, "interval": 3, "byhour": [12], "byminute": [0] } }, "jobParams": "(browserTimezone:America/New_York,layout:(dimensions:(height:2220,width:1364),id:preserve_layout),locatorParams:!((id:DASHBOARD_APP_LOCATOR,params:(dashboardId:edf84fe0-e1a0-11e7-b6d5-4dc382ef7f5b,preserveSavedFilters:!t,timeRange:(from:now-7d/d,to:now),useHash:!f,viewMode:view))),objectType:dashboard,title:'[Logs] Web Traffic',version:'9.1.0')" } ``` 3. Verify a saved object has been created using `GET .kibana_alerting_cases/_search?q=type:scheduled_report` 4. Try different requests with different schedules and notifications. It should respect the email domain allowlist if configured and reject invalid rrule schedules and email addresses. --------- Co-authored-by: Ersin Erdal <[email protected]> Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Ersin Erdal <[email protected]> Co-authored-by: Elastic Machine <[email protected]>

…ure branch) (#219770) Towards #216313 > [!Note] > This PR will be merged into a [feature branch](#221028) ## Summary This PR adds the `scheduled_report` task, which generates reports on a recurring cadence. * maxConcurrency of this task is 1 so only one can run at a time * this task shares concurrency with the existing `report:execute` task, so only one of either task type can run at a time * this task requires an API key to run so it will only run when ES security and API keys are enabled and a permanent encryption key for Kibana is set * when the task runs, it creates a new `ReportSource` document in the `.kibana-reporting` index that stores the final base64 encoded generated output. This `ReportSource` matches the data model of existing reports with the addition of a `scheduled_report_id` field which links to the scheduled report saved object ID. ## Verify * Use the dev console to schedule some reports. * Verify the the reports get generated at the expected cadence * Verify that the correct time range is used for each scheduled report Note, the UI has not been updated to differentiate between scheduled and single run reports. They will look the same from in the report listing, except the scheduled report will have a timestamp appended to the report name. In the cloud deployment for this PR, we have an example scheduled report that is running every day at 4:45 EDT: https://kibana-pr-219770.kb.us-west2.gcp.elastic-cloud.com/app/management/insightsAndAlerting/reporting --------- Co-authored-by: Ersin Erdal <[email protected]> Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Ersin Erdal <[email protected]> Co-authored-by: Elastic Machine <[email protected]>

…220922) Towards #216313 > [!Note] > This PR will be merged into a [feature branch](#221028) ## Summary Adds internal APIs for listing and disabling scheduled reports. For this initial iteration, we are not adding an `enable` API. This adds a `Manage Scheduled Reports` feature privilege that, if the user has it, allows them to view and disable the scheduled reports of any user in the current space. ## To Verify 1. Create a user (`user1`) with the ability to generate reports but not manage reports. Use the schedule API to schedule some reports as this user. 2. Create another user (`user2`) with the ability to manage reports. Use the schedule API to schedule some reports as this user. 3. As `user1`, use the Dev Console to list scheduled reports. You should only see those created by `user1`. `user1` should also be able to disable their own reports. 4. As `user2`, use the Dev Console to list scheduled reports. You should see reports from both `user1` and `user2`. `user2` should be able to disable a report created by `user1`. --------- Co-authored-by: Ersin Erdal <[email protected]> Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Ersin Erdal <[email protected]> Co-authored-by: Elastic Machine <[email protected]>

tsullivan

LGTM! Thank you so much!

I'm really looking forward to this new feature!

elasticmachine · 2025-06-18T00:56:17Z

⏳ Build in-progress

History

💚 Build #309649 succeeded 3e78c24
💚 Build #309533 succeeded 2d6e8be
💚 Build #309352 succeeded 0b0e3a5
💚 Build #308589 succeeded 41883e1
💛 Build #308092 was flaky f5f9d9d

cc @ymao1

elena-shostak

LGTM!

Left a couple of nits

elena-shostak · 2025-06-18T10:23:02Z

x-pack/platform/plugins/private/reporting/server/lib/tasks/run_single_report.ts

+    // round up from ms to the nearest second
+    const queueTimeout =
+      Math.ceil(numberToDuration(this.opts.config.queue.timeout).asSeconds()) + 's';
+    const maxConcurrency = this.opts.config.queue.pollEnabled ? 1 : 0;


nit: we can also add function similar to getMaxAttempts

protected getMaxConcurrency() { return this.opts.config.queue.pollEnabled ? 1 : 0; }

since both RunScheduledReportTask and RunSingleReportTask extend RunReportTask, we can even move it there. Logic for getting config options seems to be the same

Updated in 48829a9

elena-shostak · 2025-06-18T10:39:02Z

...k/platform/plugins/private/reporting/server/routes/common/request_handler/request_handler.ts

+    if (req.body) {
+      const { jobParams: jobParamsPayload } = req.body;
+      jobParamsRison = jobParamsPayload ? jobParamsPayload : null;
+    } else if (req.query?.jobParams) {
+      const { jobParams: queryJobParams } = req.query;
+      if (queryJobParams) {
+        jobParamsRison = queryJobParams;
+      } else {
+        jobParamsRison = null;
+      }


Suggested change

if (req.body) {

const { jobParams: jobParamsPayload } = req.body;

jobParamsRison = jobParamsPayload ? jobParamsPayload : null;

} else if (req.query?.jobParams) {

const { jobParams: queryJobParams } = req.query;

if (queryJobParams) {

jobParamsRison = queryJobParams;

} else {

jobParamsRison = null;

}

const jobParamsRison =

req.body?.jobParams ?? req.query?.jobParams ?? null;

elena-shostak · 2025-06-18T10:46:23Z

x-pack/platform/plugins/private/reporting/server/routes/common/scheduled/scheduled_query.ts

+          auditLogger.log(
+            scheduledReportAuditEvent({
+              action: ScheduledReportAuditAction.LIST,
+              savedObject: {


we have added support for the name field in audit events in #206644

would you mind to add it here and other corresponding audit logs?

SavedObjectsUtils.getName(registry.getNameAttribute(type), savedObject)

Updated in 48829a9. Thanks for catching! I had the name field in some audit events but not others for some reason 🤦‍♀️

pmuellr · 2025-06-18T16:28:05Z

I'm not seeing the notification bits work, assume I have something set up wrong. I do have notifications.connectors.default.email, and seem to remember seeing it run at some point (outside of this PR work). No messages or anything in the logs (running at DEBUG for reporting).

~~If someone else can validate a notification works, fine with me, I'll assume I've got some wonky setup.~~

update: I wasn't running the branch with the latest commits 🤦🏻‍♂️

ymao1 · 2025-06-18T18:24:06Z

@pmuellr I set up a scheduled report on the cloud deployment to email us with a dashboard every hour on the 15 and 45 minute. I've been getting the emails...can you confirm you've been getting them?

Also, could you share your kibana config?

pmuellr · 2025-06-18T19:18:52Z

@pmuellr I set up a scheduled report on the cloud deployment to email us with a dashboard every hour on the 15 and 45 minute. I've been getting the emails...can you confirm you've been getting them?

Also, could you share your kibana config?

Sorry, I was running old code. I can see it working now! \o/

And yes, I'm getting spammed by the scheduled report you set up :-)

pmuellr

LGTM, tested with multiple users with different management feature setting, and with the notify. Quite nice! Can't wait to get a UX on here!

pmuellr · 2025-06-18T19:51:12Z

x-pack/platform/plugins/shared/notifications/server/services/types.ts

-export interface AttachmentEmail extends PlainTextEmail {
+export interface AttachmentEmail extends Omit<PlainTextEmail, 'to'> {
  attachments: Attachment[];
+  to?: string[];


Feels like this is something we shouldn't have had to do. The notifications service seems like it could use some polish - it should support at least bcc and cc as well as optional to, and probably attachments, not sure about spaceId :-). Can we open an issue to get this updated?

js-jankisalvi

Verified locally, works as expected 👍

elasticmachine · 2025-06-19T12:20:17Z

💛 Build succeeded, but was flaky

Failed CI Steps

FTR Configs #71

Test Failures

[job] [logs] FTR Configs #71 / Security Solution - alerting api integration - security and spaces enabled Alerts - Group 1 alerts backfill rule runs ad hoc backfill with rule actions should run summary actions for backfill jobs when run_actions=true

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
`@kbn/reporting-common`	90	97	+7
`taskManager`	67	71	+4
total			+11

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
`fleet`	1.8MB	1.8MB	+360.0B

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
`taskManager`	10	9	-1

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
`reporting`	50.5KB	50.8KB	+302.0B

Unknown metric groups

API count

id	before	after	diff
`@kbn/reporting-common`	100	107	+7
`taskManager`	113	117	+4
total			+11

ESLint disabled line counts

id	before	after	diff
`@kbn/test-suites-xpack`	346	349	+3

References to deprecated APIs

id	before	after	diff
`reporting`	7	9	+2

Total ESLint disabled count

id	before	after	diff
`@kbn/test-suites-xpack`	364	367	+3

History

💚 Build #309913 succeeded 48829a9
💚 Build #309675 succeeded d8b80fd
💚 Build #309649 succeeded 3e78c24
💚 Build #309533 succeeded 2d6e8be
💚 Build #309352 succeeded 0b0e3a5

cc @ymao1

kibanamachine · 2025-06-19T13:20:41Z

Starting backport for target branches: 8.19

https://github.com/elastic/kibana/actions/runs/15758885164

kibanamachine · 2025-06-19T13:27:06Z

💔 All backports failed

Status	Branch	Result
❌	8.19	Backport failed because of merge conflicts You might need to backport the following PRs to 8.19: - [Observability] [Serverless] Introduce custom roles (#219861) - Optimize bulk actions endpoint & update gaps (#222158)

Manual backport

To create the backport manually run:

node scripts/backport --pr 221028

Questions ?

Please refer to the Backport tool documentation

ymao1 · 2025-06-20T13:02:30Z

💚 All backports created successfully

Status	Branch	Result
✅	8.19

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

Resolves elastic#216313 ## Summary This is a feature branch that contains the following commits. Each individual linked PR contains a summary and verification instructions. * Schedule API - elastic#219771 * Scheduled report task runner - elastic#219770 * List and disable API - elastic#220922 * Audit logging - elastic#221846 * Send scheduled report emails - elastic#220539 * Commit to check license - elastic@f5f9d9d * Update to list API response format - elastic#224262 --------- Co-authored-by: Ersin Erdal <[email protected]> Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Ersin Erdal <[email protected]> Co-authored-by: Elastic Machine <[email protected]> Co-authored-by: Alexi Doak <[email protected]> (cherry picked from commit a409627) # Conflicts: # src/platform/packages/private/kbn-reporting/common/routes.ts # x-pack/platform/plugins/private/canvas/server/feature.test.ts # x-pack/platform/plugins/private/reporting/server/core.ts # x-pack/platform/plugins/private/reporting/server/features.ts # x-pack/platform/plugins/shared/features/server/__snapshots__/oss_features.test.ts.snap # x-pack/platform/test/api_integration/apis/features/features/features.ts # x-pack/test_serverless/api_integration/test_suites/chat/platform_security/authorization.ts # x-pack/test_serverless/api_integration/test_suites/observability/platform_security/authorization.ts # x-pack/test_serverless/api_integration/test_suites/search/platform_security/authorization.ts # x-pack/test_serverless/api_integration/test_suites/security/platform_security/authorization.ts

## Summary > [!IMPORTANT] > This PR is targeting the `scheduled-reports-ui` feature branch, where the backend changes from the `scheduled-reports` branch are temporarily integrated while waiting for #221028 to be merged (see the squashed `[TMP] ...` commit message). Implements the flyout UI for the creation and read-only viewing of scheduled reports (exports). <img height="500" alt="image" src="https://github.com/user-attachments/assets/6bbd274b-1bbb-481f-ac40-4d7131be6d85" /> <details> <summary> ## Known issues </summary> - Console error due to `compressed` attribute wrongly forwarded by form-hook-lib to DOM element (this is likely a form lib issue): <img width="916" alt="image" src="https://github.com/user-attachments/assets/09d20ba9-8781-46d6-bcfa-862d8a4cbf90" /> - Email validation errors accumulate instead of replacing the previous one (again looks like a fom lib issue): https://github.com/user-attachments/assets/f2dc7a46-a3a9-465d-b8a1-3187b200f9b9 </details> <details> <summary> ## Screenshots </summary> Health API error: <img height="500" alt="Screenshot 2025-05-31 at 10 48 40" src="https://github.com/user-attachments/assets/dd069597-971c-489f-9c07-eb5edfd7bede" /> Health API loading state: <img height="500" alt="Screenshot 2025-05-31 at 10 49 04" src="https://github.com/user-attachments/assets/27d95bf3-bf7d-42c7-9a40-2826f38aa837" /> Health API success with some missing prerequisites: <img width="449" alt="Screenshot 2025-06-17 at 16 59 57" src="https://github.com/user-attachments/assets/c44afa97-70ff-4618-8b73-41b816514459" /> Form validation: <img height="500" alt="image" src="https://github.com/user-attachments/assets/a8d4cae1-2819-4f71-a911-9300a6cf81f8" /> Success toast: <img width="480" alt="image" src="https://github.com/user-attachments/assets/a87c3af5-dbb0-40e8-915a-fc9d7e1d97f2" /> Failure toast: <img width="518" alt="image" src="https://github.com/user-attachments/assets/908f9dea-b5cb-4da9-b4a5-76e313837f18" /> Print format toggle: <img width="502" alt="image" src="https://github.com/user-attachments/assets/602f3ab9-07ef-4689-a305-dc1b2b5495cd" /> Missing notifications email connector callout: <img width="499" alt="image" src="https://github.com/user-attachments/assets/fe4997a5-75e6-4450-85e5-7d853049e085" /> </details> ## References Closes #216321 Stacked on #220535 --------- Co-authored-by: kibanamachine <[email protected]> Co-authored-by: Eyo O. Eyo <[email protected]>

…224354) ## Summary Resolves #216322 > [!IMPORTANT] > This PR is targeting the `scheduled-reports-ui` feature branch, where the backend changes from the `scheduled-reports` branch are temporarily integrated while waiting for #221028 to be merged (see the squashed `[TMP] ...` commit message). > This PR has few commits from #222135 to support view schedule config table action. Please ignore code changes in folders if you are already reviewing other PR. `src/platform/packages/private/kbn-reporting/public/share/share_context_menu`, `src/platform/packages/shared/response-ops/recurring-schedule-form`, `x-pack/platform/plugins/private/reporting/public/management/schemas`, `x-pack/platform/plugins/private/reporting/public/management/validators` and `xpack/platform/plugins/shared/alerting/public/pages/maintenance_windows/components/create_maintenance_windows_form.tsx`. This PR adds new tabs `Exports` and `Schedules` in Reporting section. `Exports` tab shows the list of all reports. Allows to open dashboard, download report and view report information. `Schedules` tab shows list of scheduled reports. Allows to disable schedule. ### Checklist Check the PR satisfies following conditions. - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios ### What to test - Verify tabs - Verify exports table shows list of all reports - Verify schedules table shows list of scheduled report - Verify you can disable scheduled report - Verify pagination in both tables --------- Co-authored-by: kibanamachine <[email protected]>

kibanamachine · 2025-06-23T13:49:43Z

Looks like this PR has a backport PR but it still hasn't been merged. Please merge it ASAP to keep the branches relatively in sync.
cc: @ymao1

# Backport This will backport the following commits from `main` to `8.19`: - [[Response Ops][Reporting] Scheduled Reports (#221028)](#221028)  ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)  --------- Co-authored-by: kibanamachine <[email protected]>

ymao1 self-assigned this May 20, 2025

Merge branch 'main' of github.com:elastic/kibana into scheduled-reports

a7065b2

This was referenced May 20, 2025

[Response Ops][Reporting] Scheduled Reports - Task (merging into feature branch) #219770

Merged

[Response Ops][Reporting] Scheduled Reports - List and Disable API #220922

Merged

Merge branch 'main' of github.com:elastic/kibana into scheduled-reports

717ebba

ymao1 force-pushed the scheduled-reports branch from d0dd7b3 to 717ebba Compare May 23, 2025 13:48

ymao1 added 2 commits May 23, 2025 09:48

Merge branch 'main' of github.com:elastic/kibana into scheduled-reports

37e7fd2

Merge branch 'main' of github.com:elastic/kibana into scheduled-reports

08db312

ymao1 mentioned this pull request May 28, 2025

[Response Ops][Reporting] Scheduled Reports - Audit Logging (merging into feature branch) #221846

Merged

Merge branch 'main' of github.com:elastic/kibana into scheduled-reports

577b517

ymao1 mentioned this pull request May 30, 2025

[Response Ops][Reporting] Retry scheduled reporting task #222079

Closed

ymao1 added ci:cloud-deploy Create or update a Cloud deployment ci:cloud-persist-deployment Persist cloud deployment indefinitely labels May 30, 2025

Merge branch 'main' of github.com:elastic/kibana into scheduled-reports

6010d6a

ymao1 mentioned this pull request May 31, 2025

Adding scheduled_report_id field to kibana reporting template elastic/elasticsearch#127827

Merged

doakalexi mentioned this pull request Jun 2, 2025

[ResponseOps][Reporting] Send email with report attachment for scheduled reporting task (merging into feature branch) #220539

Merged

1 task

ymao1 and others added 4 commits June 6, 2025 09:56

Merge

12d8064

Merge branch 'main' of github.com:elastic/kibana into scheduled-reports

eb2cb21

Merge branch 'main' of github.com:elastic/kibana into scheduled-reports

3b44fb3

tsullivan approved these changes Jun 18, 2025

View reviewed changes

elena-shostak self-requested a review June 18, 2025 09:02

elena-shostak approved these changes Jun 18, 2025

View reviewed changes

PR feedback - name in audit log

48829a9

pmuellr approved these changes Jun 18, 2025

View reviewed changes

dokmic approved these changes Jun 19, 2025

View reviewed changes

js-jankisalvi mentioned this pull request Jun 19, 2025

[ResponseOps] [Reporting] Allow users to see scheduled reports list #224354

Merged

1 task

js-jankisalvi approved these changes Jun 19, 2025

View reviewed changes

Merge branch 'main' of github.com:elastic/kibana into scheduled-reports

3db7db6

ymao1 enabled auto-merge (squash) June 19, 2025 11:38

ymao1 merged commit a409627 into main Jun 19, 2025
10 checks passed

ymao1 deleted the scheduled-reports branch June 19, 2025 13:20

kibanamachine mentioned this pull request Jun 19, 2025

Implement functionality to add observables, procedures and custom fields to alerts for TheHive #207255

Merged

7 tasks

ymao1 mentioned this pull request Jun 20, 2025

[8.19] [Response Ops][Reporting] Scheduled Reports (#221028) #224692

Merged

kibanamachine mentioned this pull request Jun 23, 2025

[Dataset quality] degradedDocs rule #216026

Merged

kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Jun 23, 2025

kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Jun 23, 2025

[Response Ops][Reporting] Scheduled Reports #221028

[Response Ops][Reporting] Scheduled Reports #221028

Uh oh!

Conversation

ymao1 commented May 20, 2025 • edited by kibanamachine Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Uh oh!

tsullivan left a comment

Choose a reason for hiding this comment

Uh oh!

elasticmachine commented Jun 18, 2025

⏳ Build in-progress

History

Uh oh!

elena-shostak left a comment

Choose a reason for hiding this comment

Uh oh!

elena-shostak Jun 18, 2025

Choose a reason for hiding this comment

Uh oh!

ymao1 Jun 18, 2025

Choose a reason for hiding this comment

Uh oh!

elena-shostak Jun 18, 2025

Choose a reason for hiding this comment

Uh oh!

elena-shostak Jun 18, 2025

Choose a reason for hiding this comment

Uh oh!

ymao1 Jun 18, 2025

Choose a reason for hiding this comment

Uh oh!

pmuellr commented Jun 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ymao1 commented Jun 18, 2025

Uh oh!

pmuellr commented Jun 18, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pmuellr left a comment

Choose a reason for hiding this comment

Uh oh!

pmuellr Jun 18, 2025

Choose a reason for hiding this comment

Uh oh!

js-jankisalvi left a comment

Choose a reason for hiding this comment

Uh oh!

elasticmachine commented Jun 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

Metrics [docs]

Public APIs missing comments

Async chunks

Public APIs missing exports

Page load bundle

API count

ESLint disabled line counts

References to deprecated APIs

Total ESLint disabled count

History

Uh oh!

Uh oh!

kibanamachine commented Jun 19, 2025

Uh oh!

kibanamachine commented Jun 19, 2025

💔 All backports failed

Manual backport

Questions ?

Uh oh!

ymao1 commented Jun 20, 2025

💚 All backports created successfully

Questions ?

Uh oh!

kibanamachine commented Jun 23, 2025

Uh oh!

ymao1 commented May 20, 2025 •

edited by kibanamachine

Loading

pmuellr commented Jun 18, 2025 •

edited

Loading

pmuellr commented Jun 18, 2025 •

edited

Loading

elasticmachine commented Jun 19, 2025 •

edited

Loading