[COMPASS-4366] Is it possible for you to reduce Bugsnag Events compass sends? Created: 24/Jul/20  Updated: 29/Oct/23  Resolved: 30/Nov/21

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Critical - P2
Reporter: James Broadhead (Inactive) Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to COMPASS-4369 Fix `Uncaught Error: Callback was alr... Closed
Documentation Changes: Not Needed

 Description   

Hi there!

Bugsnag is used by 4 teams internally; Cloud, Compass, MANA and University.
Of these, Compass seems to be producing around 2/3 of our daily events - which are sometimes pushing us over our daily limit, leading to sampling.

https://app.bugsnag.com/settings/mongodb/usage?i=em&m=hl

Are you making use of all of these events?
Is there a way that the number being sent could be reduced? [not urgent]

I'm working with Procurement on our renewal with bugsnag.
Buying more daily events would bring our cost from $8k/yr to $22k/ yr
If you can't reduce the event-count, can you pay for this increase from your team's budget?

Priority note: since the renewal decision is due soon, I'm calling this a P2 for the decision - but not on reducing the event count, which can be done on a more flexible timeline



 Comments   
Comment by Rhys Howell [ 30/Nov/21 ]

Closing since we've turned off our error logging in bugsnag.

Comment by James Broadhead (Inactive) [ 29/Jul/20 ]

brilliant - thank you!

Generated at Wed Feb 07 22:36:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.