I got to know about Sentry because they have a special offer for students, through the GitHub Student Developer Pack[0]. I searched for Sentry right now, through the search, and I am surprised how common it was to talk about these tools.

If it wasn't for the GitHub pack, I would have never known about something like this. Maybe you are right, and it isn't a unique enough topic now :(

[0] https://education.github.com/pack

I know Sentry and hotjar from noscript panel.

I disable javascript by default, some sites become non-functional, then I enable 1st party js, and something see these 3rd party js and got curious on it when I see it being used from multiple sites.

You can also quickly see which tech are used by the site you're browsing with the wappalyzer addon

Observability has never been sexy. It's a lot of grunt work and boilerplate.

That being said, New Relic has served us fairly well. Especially if you put in the grunt work for distributed tracing between the client and your servers.

At least for me when building things the first thing I install after setting up a project is Sentry.

They have a generous free tier and are open source so that’s a plus too

https://sentry.io/pricing/ ...if you're gonna go looking.

For browser side,

Report-uri is the tool. Warning you are going to get a lot of reports because your stuff is broken a lot. You just don't see it.

I always give that advice when adding these sorts of tools into the mix. "you are about to get a lot of work you did not know you had".

Basically more than likely your code/infrastructure is doing something wrong. These linter style tools many times will find whole classes of bugs smeared across your whole code base.

One poor soul I worked with once decided 'hey no errors are being caught anywhere'. He then proceeded to add logging to everything where something would fail. "dude you are about to get 1000 bugs back from the QA group and they will blame you even though it is the 3 guys who left 2 years ago that did it". He nearly lost his job because he did not prime them for it. QA was rightly mad because they went from 'everything seems to work' to error alerts everywhere and no testing can be completed.

Tools like Sentry are not just collection, but more importantly do aggregation.

I've built shopping cart forms before, which get every single browser imaginable. Keenly aware of the number of oddball edge case errors that happen.

I don't see in Sentry where you can set up "Report-To", "NEL" headers.