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.

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, a cron job runs on atd-data02. 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: https://github.com/cityofaustin/atd-data-tech/issues/5952

• Slack thread: https://austininnovation.slack.com/archives/CNUEPKLB1/p1657661751327599