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

Add metrics to track how often events are soft_failed #10156

Merged
merged 5 commits into from
Jun 11, 2021
Merged

Add metrics to track how often events are soft_failed #10156

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
1d6b946
Add metrics for how often events are soft_failed
MadLittleMods Jun 9, 2021
c71f2c1
Add changelog
MadLittleMods Jun 9, 2021
7d97ee8
Update metric name to follow prometheus standards
MadLittleMods Jun 11, 2021
fa4cf59
Update soft failed to be human readable in changelog
MadLittleMods Jun 11, 2021
2970bac
Fill in metric description
MadLittleMods Jun 11, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions synapse/handlers/federation.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,7 @@
)

import attr
from prometheus_client import Counter
from signedjson.key import decode_verify_key_bytes
from signedjson.sign import verify_signed_json
from unpaddedbase64 import decode_base64
Expand Down Expand Up @@ -101,6 +102,8 @@

logger = logging.getLogger(__name__)

soft_failed_event_counter = Counter("synapse_handlers_federation_soft_failed_event", "")


@attr.s(slots=True)
class _NewEventInfo:
Expand Down Expand Up @@ -2498,6 +2501,7 @@ async def _check_for_soft_fail(
event_auth.check(room_version_obj, event, auth_events=current_auth_events)
except AuthError as e:
logger.warning("Soft-failing %r because %s", event, e)
Copy link
Contributor Author

@MadLittleMods MadLittleMods Jun 11, 2021 •
edited
Loading

Choose a reason for hiding this comment

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

For the future:

If we want to dig deeper into what rooms are soft_failing messages, we could use the Elasticsearch logs and some aggregations (Kibana or raw ES queries). We can add a few fields to the Elasticsearch mapping, room_id, mxid, event_id which should handle the high cardinality(lots of different values) just fine.

It looks like we use Logstash or Filebeat and I assume there is a way we can parse another field out besides message? Maybe https://stackoverflow.com/q/40460830/796832

-- #10156 (comment)

To document my additional findings here;

We can already use logger.info('foo', extra={ "foo": "bar"}) as shown in tests/logging/test_terse_json.py#L64-L74 to add extra fields to the structured logging.

Copy link
Contributor Author

@MadLittleMods MadLittleMods Jun 12, 2021

Choose a reason for hiding this comment

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

Created #10168 to add these fields

soft_failed_event_counter.inc()
event.internal_metadata.soft_failed = True

async def on_get_missing_events(
Expand Down