Skip to content
This repository was archived by the owner on Apr 26, 2024. It is now read-only.

Improve the logging when handling a federation transaction#3904

Merged
richvdh merged 7 commits into
developfrom
rav/rx_txn_logging
Sep 19, 2018
Merged

Improve the logging when handling a federation transaction#3904
richvdh merged 7 commits into
developfrom
rav/rx_txn_logging

Conversation

@richvdh
Copy link
Copy Markdown
Member

@richvdh richvdh commented Sep 18, 2018

Let's try to rationalise the logging that happens when we are processing an incoming transaction, to make it easier to figure out what is going wrong when they take ages. In particular:

  • make everything start with a [room_id event_id] prefix
  • make sure we log a warning when catching exceptions rather than just turning them into other, more cryptic, exceptions.

Let's try to rationalise the logging that happens when we are processing an
incoming transaction, to make it easier to figure out what is going wrong when
they take ages. In particular:

- make everything start with a [room_id event_id] prefix
- make sure we log a warning when catching exceptions rather than just turning
  them into other, more cryptic, exceptions.
@richvdh richvdh requested a review from a team September 18, 2018 16:09
Comment thread synapse/handlers/federation.py Outdated
Copy link
Copy Markdown
Member

@erikjohnston erikjohnston left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Woo! \o/

Just a minor quibble about ignoring vs queuing but I don't really care that much about it

Comment thread synapse/handlers/federation.py Outdated
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants