> For the complete documentation index, see [llms.txt](https://atd-dts.gitbook.io/moped-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atd-dts.gitbook.io/moped-documentation/dev-guides/activity-log/hasura-event-logs-and-truncate-cron-job.md). # Hasura Event Logs and Truncate Cron Job Event triggers are tracked through two tables that are managed by Hasura. 1. `hdb_catalog.event_log`: captured events 2. `hdb_catalog.event_invocation_logs`: HTTP requests and responses You can find out more about these tables by reading more [here](https://hasura.io/docs/latest/event-triggers/clean-up/). TLDR: Hasura leaves it up to us to clean up these tables so we have as much history as we like. To clean up these tables, we previously used a cron job running on our on-prem server. See: * Path to one of the scripts: `/root/automated-tasks/atd-moped/scripts/moped-production-backup-daily.sh` * AWS S3 bucket to hold backups: `atd-moped-db-backups` * The GH issue: * Slack thread: