Tag Honeybadger exceptions sent during maintenance windows so we can filter them out

tpendragon commented 4 months ago

We want to investigate network problems, but are having a hard time collating the data because of all the exceptions that happen during patch times.

We think maintenance time is:

5:30 AM - 8:30 AM Eastern Monday for Staging 5:30 AM - 8:30 AM Eastern Tuesday for Production

Maybe there's a way we can send exceptions during this window but tag them so we can easily filter them out? Send it as a different environment or something?

Acceptance Criteria

[ ] During the hours above, if an exception is fired, we don't see it in honeybadger (or can, but can filter it out would be even better)

Sudden Priority Justification

Doing this work will open up investigating networking problems we've had for a long time, and reduce our maintenance and cognitive overhead.

First Step

Look up the honeybadger documentation to see if we can control what it sends at specific times of the day.

Might use https://docs.honeybadger.io/lib/ruby/getting-started/ignoring-errors/#ignore-programmatically

tpendragon commented 2 months ago

I'm going to implement this in Pulfalight first, since there's a good staging URL that will throw an error:

https://findingaids-staging.princeton.edu/collections/MC197%20james%20addison%20baker%20papers%20at%20the%20seeley%20g.%20mudd%20manuscript%20library,%20princeton%20university

tpendragon commented 2 months ago

https://github.com/pulibrary/pulfalight/pull/1422 does this for Pulfalight. We need it in our other apps:

[x] Figgy https://github.com/pulibrary/figgy/pull/6469
[x] DPUL https://github.com/pulibrary/dpul/pull/1548
[x] LAE https://github.com/pulibrary/lae-blacklight/pull/390
[x] AbID https://github.com/pulibrary/abid/pull/172
[x] Pulmap https://github.com/pulibrary/pulmap/pull/1223

pulibrary / figgy