-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metric notification drops #33
Labels
Comments
pjenvey
added a commit
that referenced
this issue
Jul 20, 2018
to avoid passing them around everywhere (eventually we'll move message_month as well we're fully migrated) Issue #33
pjenvey
added a commit
that referenced
this issue
Jul 20, 2018
pjenvey
added a commit
that referenced
this issue
Jul 20, 2018
pjenvey
added a commit
that referenced
this issue
Jul 20, 2018
to avoid passing them around everywhere (eventually we'll move message_month too when we're fully migrated) Issue #33
pjenvey
added a commit
that referenced
this issue
Jul 20, 2018
pjenvey
added a commit
that referenced
this issue
Jul 20, 2018
to avoid passing them around everywhere Issue #33
pjenvey
added a commit
that referenced
this issue
Jul 20, 2018
pjenvey
added a commit
that referenced
this issue
Jul 20, 2018
to avoid passing them around everywhere Issue #33
pjenvey
added a commit
that referenced
this issue
Jul 20, 2018
pjenvey
added a commit
that referenced
this issue
Jul 20, 2018
to avoid passing them around everywhere Issue #33
pjenvey
added a commit
that referenced
this issue
Jul 20, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The dynamodb notification loading has a few spots where messages will be dropped silently that fail deserialization. We should do basic metric counters on these just so that we understand how frequently it happens and whether we need more detailed logging of these occurrences.
The text was updated successfully, but these errors were encountered: