search

magenizr / Magenizr_Raygun

Connect Adobe Commerce with Raygun and never let another error go unnoticed again. Monitor your full tech stack across both desktop and mobile, with all the information you need to take action.
0 stars 0 forks source link

Remove default custom hostnames when setting up #4

Closed sumitramanga closed 1 day ago

sumitramanga commented 1 week ago

Again, it is safe to say that if the API Key is added, then they are intending to set up Raygun's features! Spotting errors locally I would say is essential to not deploying bad code into production. So users can capture their errors as earlier as possible. Also, discoverability wise, they won't encounter this until they turn it on. At least when it's turn on, they can see what the impact is :)

magenizr commented 1 week ago

Hi @sumitramanga

We had cases in Laravel projects where local and staging environments ( particularly cron jobs ) have pushed a large amount of fatal errors to the live account of Raygun and triggered false alerts.

How about moving Excluded Hostnames to the developer section and leave it disabled by default?

sumitramanga commented 1 week ago

Hi @magenizr In that case, I think we leave it as is! Perhaps we need a feature to avoid cron job errors from coming through instead. that could be a possibility? Just trying to find a way of integrating Raygun in local development so that production errors by real users can be avoided

magenizr commented 1 day ago

Hi @sumitramanga

This has been moved to the Developer section and will be available in the next release.

20240704-raygun-backend-02 (1)

As discussed earlier, we'll leave the feature available for now so that developers can turn off Raygun completely for certain environments. Errors triggered by cronjob are not easy to identify unfortunately.

Regards, John

magenizr commented 1 day ago

Release 1.1.1 has been published, thank you for your contribution 👍