clockwork VS Sentry

Either Clockwork or Debugbar.

https://underground.works/clockwork/ is super easy to set up and really good.

xDebug if digging deep, otherwise I often do common profiling/performance checking via clockwork.

Solid advice, but I think you made a typo, the correct spelling of "debugbar" is "Clockwork"

90% of what I do is Laravel work and for every project, I use Clockwork. It puts all of the stuff below into a tab in Chrome's DevTools.

Funny timing — I just spent 4 hours this morning comparing Xdebug, Blackfire, and New Relic.

After feeling like my SaaS application is starting to hit some scaling bottlenecks, I had a play with all 3 services to try and get some insight for a real-world application.

A brief summary:

- Xdebug: Slow. Fiddly to set up. Fine for a development environment and day-to-day profiling, but things like Clockwork[0] are, practically speaking, far more insightful.

- Blackfire: Terrible UX. Difficult setup process. Their free plan is almost impossible to evaluate as it only shows you glorified stack traces, most of which are littered with vendor and framework files. I didn’t want to commit to paying a full year of their standard plan (no monthly payment unless options, unless you go for the highest tiers), so I happily uninstalled and moved on.

- New Relic: wow… one command and a server reboot later, and I’m seeing performance profiling, consolidated dashboards, error logging, MariaDB and Redis queries, frontend performance, and server capacities - with REAL data, on production! I’m very, very impressed. And it’s free for a single user…?!

[0] Clockwork: https://underground.works/clockwork/

Sentry: Error monitoring for applications, including APIs. Also offers application performance monitoring (APM).

Indeed, webapps are not immune to distribution problems. Wayward and invasive browser extensions are a clear threat, as are 3rd-party dependencies (and their dependencies) loaded at runtime. Which is why companies like https://sentry.io exist. I think the difference is that webapps are "distributable by default" and it takes real work to break this. Versus having local desktop apps which require work to distribute. A potent example of the power of defaults.

> You invent something, and then immediately turn it into a cheap commodity by releasing it for free.

Exactly. A 71-line python script https://github.com/getsentry/sentry/commit/3c2e87573d3bd16f6... was groundbreaking when it came out and the fact that it springboarded into a startup is commendable.

Sentry - Open Source Alternative For Error Tracking

11. Sentry

Visit the website https://sentry.io/ and create your account.

https://github.com/getsentry/sentry/pull/60144 -> https://github.com/getsentry/sentry/blob/d4d89e2fa93ad99f13d...

If they're going to all this trouble for "ambiguity," I don't know why they wouldn't further extend their custom SPDX identifier to include the "2 year" rollover, since that's one of their pearl-clutching reasons for this bullshit: https://github.com/getsentry/loose-confederation/issues/4

It's source available under the BSL: https://github.com/getsentry/sentry. After four years it becomes open source (probably to prevent "AWS Elastic Error Handling service(tm)" from becoming a thing)

You can still run it for your company for free, if you feel like managing all of the infra it requires.

Ohh, I forgot to mention that I added Sentry in this project just because it is an easy way to track the errors. But don’t worry, it is free and you can create it here.