The Moped activity log tracks changes to records in specified database tables. These records are stored in the moped_activity_log table.
The previous architecture used SQS + Lambda do to manage activity log events, but those components have since been removed.
The activity log works by configuring Hasura Event Triggers on any table/column that needs to be tracked. When an insert or update event is triggered, the Hasura event trigger is configured to use REST Connectors to send an insert mutation into the moped_activity_log table.
