What is the difference between Telescope, Pulse, and Horizon?

[fast vine]

Hi!
I want to implement something that will let me debug the app in production and development if there are any issues. I know that Horizon is primarily for queues, but how does that differ from something like Pulse and Telescope? And what's the difference between those 2 as well? It looks like Telescope goes way more in depth with stuff, but does the same thing as Pulse.

The only thing I've heard is that Telescope slows down the website because it tracks everything, so Pulse is a bit lighter in that sense, but I haven't seen anything else about them.

Thanks!

[covert forge]

I'd strongly recommend to think better how to title your question. Ask the "difference between" those 3 tools is an invitation to infame comments like "read the docs". Or some people will preffer to ignore a just scroll it up. But I get what you mean.

First, I think you should not want to "debug" the app in production. Setup some error report tool like Sentry to get notified and work on errors.

But getting back to your question, Telescope will give you more details and record all requests. But as you pointed out, it is not for production. You can have it in your online staging environment, clone your production db and test the requests against same data if you think it makes sense.

It might be acceptable to enable Telescope in production for a short períod to get some examples, depending on your business, but not so good idea.

Horizon is for queue management. Period. You should not even have included in this list.

Then, we have Pulse, that is a new tool in the ecosystem meant to be used in production, and can help you to monitor. Pay attention: "monitor" your app, not "debug". It will tell you that a query is slow, for example. So go to the logs and check your db structure. Not exactly a debug, but can give great insight.