Skip to content

feat: execution log persistence to TimescaleDB (#272)#380

Open
Daveside9 wants to merge 1 commit intoEDOHWARES:mainfrom
Daveside9:feat/issue-272-timescaledb-execution-logs
Open

feat: execution log persistence to TimescaleDB (#272)#380
Daveside9 wants to merge 1 commit intoEDOHWARES:mainfrom
Daveside9:feat/issue-272-timescaledb-execution-logs

Conversation

@Daveside9
Copy link
Copy Markdown

Closes #272 — Execution Log Persistence to TimescaleDB

Sets up TimescaleDB as a time-series store for trigger execution events. Every execution (success, failure, batch) is persisted as a hypertable row from both the queue and direct execution paths. Includes a migration worker to backfill historical data from MongoDB, optimised trend queries via continuous aggregates, a REST API for execution history and health stats, unit tests, and documentation.

@drips-wave
Copy link
Copy Markdown

drips-wave Bot commented Apr 29, 2026

@Daveside9 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Backend: Execution Log Persistence strategy to TimescaleDB

1 participant