mozilla-releng/balrog

handle or ignore new types of bad data being sent to balrog

Closed this issue · 1 comments

I noticed a couple of new, fairly spammy types of queries being sent to Balrog production. They are:

These show up in Sentry as quite high volume events, which makes it more difficult to find real issues (eg: ones that affect real builds in the wild). At this volume, it also causes us to spin up extra pods due to all the churn of sending these events to Sentry.