Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add metric to count number of packets filtered due to memo or receiver being too big #3794

Closed
5 tasks
ljoss17 opened this issue Jan 18, 2024 · 0 comments · Fixed by #3795
Closed
5 tasks

Add metric to count number of packets filtered due to memo or receiver being too big #3794

ljoss17 opened this issue Jan 18, 2024 · 0 comments · Fixed by #3795

Comments

@ljoss17
Copy link
Contributor

ljoss17 commented Jan 18, 2024

Description

Following the addition of a filter for memo and receiver fields too big #3766, adding a metric to measure how many packets have been filtered with this feature could help identify issues with big packets.

For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate milestone (priority) applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@github-project-automation github-project-automation bot moved this to 🩹 Triage in Hermes Jan 18, 2024
@ljoss17 ljoss17 mentioned this issue Jan 18, 2024
Merged
7 tasks
@github-project-automation github-project-automation bot moved this from 🩹 Triage to ✅ Done in Hermes Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Hermes
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add memo and/or receiver filter metric informalsystems/hermes
1 participant
@ljoss17