Change event logging mechanism

[amirfz]

Description

Describe your pull request here. What does this change implement or fix? Include motivation and context, e.g. relevant logs, error output, etc.

Add directions for contributors. For example, do developers need to run poetry install after picking up these changes?

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Maintenance
• New release

Related issues

Mention related GitHub and Linear issues. E.g. Closes #xxx or Fixes #xxx. Otherwise delete this section.

Checklists

To speed up the review process, please follow these checklists:

Development

• The Pull Request is small and focused on one topic
• Lint rules pass locally (make format && make lint)
• The code changed/added as part of this pull request has been covered with tests
• All tests related to the changed code pass in development (make test)
• The changes generate no new warnings (or explain any new warnings and why they're ok)
• Commit messages are detailed
• Changed code is self-explanatory and/or I added comments
• I updated the documentation (docstrings, /docs)
  See the testing guidelines for help on tests, especially those involving web services.

Code review

• This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached.
• I have performed a self-review of my code
• Issue from task tracker has a link to this pull request

💔 Thank you for submitting a pull request!