event sourcing vs database triggers for auditing

hey folks, im wrestling with how best to implement auditing in a new system. we need to track changes to core entities, and im weighing two main approaches: event sourcing for the primary data store, or sticking with a more traditional relational db and using triggers to log changes. event sourcing feels more 'correct' for immutability and history, but also brings its own complexities. triggers are simpler to implement initially but can become a maintenance headache and might impact write performance. what are your experiences with these patterns for auditing? any horror stories or unexpected benefits?