Open sentry-io[bot] opened 3 years ago
This is eating through our Sentry quota so let's add some error handling here.
I don't currently have the bandwidth for this right now and as it's a non breaking issue isn't my top priority.
@ilyastrodubtsev you think you could take a look at this early next week?
A quick look the easiest fix would be to just add it so it ignores it.
If you mean 'Ignore' in Sentry, it will still count towards the quota as it traverses their ingress.
I mean add it to the sentry configuration in the program to not send to sentry.
Sure, that works.
Related to NebraLtd/hm-diag#48
I've temporarily disabled sentry out of the diagnostics for now so this should stop spamming sentry as much.
Do we need sentry to be disabled? Or can we just fix this issue?
ERROR:dbus.proxies:Introspect error on :1.99:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NotSupported: org.freedesktop.DBus.Introspectable.Introspect
Yes, Sentry is disabled at the moment, so the objective of this ticket is to:
FYI this is still occuring...
ERROR:dbus.proxies:Introspect error on :1.2226:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NotSupported: org.freedesktop.DBus.Introspectable.Introspect
gateway-config DEBUG:root:Wi-Fi Scanning
gateway-config DEBUG:root:Wi-Fi Complete
gateway-config DEBUG:root:Write Add Gateway
gateway-config ERROR:dbus.proxies:Introspect error on :1.706:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NotSupported: org.freedesktop.DBus.Introspectable.Introspect
gateway-config DEBUG:dbus.proxies:Executing introspect queue due to error
gateway-config DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): o571444.ingest.sentry.io:443
gateway-config DEBUG:urllib3.connectionpool:https://o571444.ingest.sentry.io:443 "POST /api/5725518/store/ HTTP/1.1" 200 41
gateway-config DEBUG:root:Adding Response
gateway-config DEBUG:root:Read Add Gateway
gateway-config DEBUG:root:Wi-Fi Scanning
gateway-config DEBUG:root:Wi-Fi Complete
Hey team! Please add your planning poker estimate with ZenHub @ilyastrodubtsev @vladimirpoleshko @vpetersson
This error is still happening in hm-config but has not appeared in hm-diag for a month. This was potentially addressed by the last refactor. Lets consider closing this in the future.
Relocated to hm-config because hm-diag no longer uses dbus
Sentry Issue: HM-DIAG-2
This also happens in hm-config: https://github.com/nebraltd/hm-config/issues/31