How are you debugging on a live server?

Wappler General Need Help
1

Hi everyone !

A question I’m starting to ask myself is how I will in the future debug when customers report errors on my production server.

For the moment my error page have a section with information I display for the user to report, date of report, type of error, etc.

When my tester are reporting to me errors I use Wappler to switch to their target and display logs, but I find it painful to navigate through it.

How are you debugging your live servers? Are you using Wappler, ssh, or a tool from your hosting? Any improvment planned for this from the team, adding date and time in logs for example?

2

i think tools like these might be of some help:



clarity.microsoft.com

1 Like
3

What do you need to debug? Client? Server?
What backend are you using? PHP, nodejs, ASP?

4

I want to debug NodeJS backend.

5

For that you can use chrome developer tools for nodejs.

6

I want to debug error that my customer have, I can’t go on there computer use the dev tools, or maybe I can, not sure?

Let say my customer have an error today, I want to be able to check logs at that time and see what was the error to know how to fix it.

7

I see. As your title said debugging live servers I though you wanted that. You are actually looking for a logging and tracing app.

Then Sentry is a good choice as mentioned by @nshkrsh

There is a commercial SaaS version with a free tier and a 100% free self-hosted one.

Wappler team and I can vouch for it as we both use it. Maybe others do too.

2 Likes
8

we've used LogRocket extensively - was very helpful with screen recording and logging of http requests.
if its purely UI based, maybe MS Clarity would be better, free an easy to setup and free.
Posthog, Sentry if you want much more.

1 Like