89799969 opened a new pull request, #4382: URL: https://github.com/apache/rocketmq-dashboard/pull/4382
Fixes #3559. ## Problem Ops > Notification Deliveries has no export action. After a webhook/SMTP outage, operators who need to share the failed deliveries with another team have to copy rows manually. Topics, consumer groups, studio users, system alerts and audit logs already offer CSV export. ## Change Follow the existing system-alerts export pattern (client-side paging + shared CSV writer): - Add an "Export CSV" button on the deliveries page that pages through the **currently filtered** channel / status / instance set (100 rows per page, capped at 100 pages = 10,000 rows). - Export operationally relevant fields only — delivery id, alert id/title/domain/transition, instance, channel, status, attempt count, created/delivered/next-attempt timestamps and last error. Full notification message content is **not** exported. - Cells go through the shared `buildCsv` writer (quoted + formula-injection safe). - Add zh/en strings for the button and result toasts. ## Verification ```bash cd web && npm test -- --run src/pages/ops/__tests__/NotificationDeliveriesPage.test.tsx ``` 4 tests passed, including the new `exports the filtered deliveries across pages as CSV` regression (multi-page fetch, column set, no message content, deterministic filename). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
