chore: add log on coral stream raising an error
If the initialisation of the client object raise and exception we are not caching it and not logging it. With these changes we track the error in that case.
Why ? We do this because a lot of users are reporting coral initialisation errors , we need to collect data to support this reports
Hey @juanSanchezAlcala, you may also be interested in o-errors to implement this. Sends errors to Sentry. It's an old library and I have no idea if/how it's used by Customer Products 🙈 So, just a suggestion to take a quick look. I have no problem with a custom tracking event
Closing this as it's been open for a while. Please let me know if you would like to revisit this PR.