Next step · What to do next

See errors that visitors hit (error tracking and logs)

What you may see

I want to know when something breaks for a customer

Why this step

Errors that happen on visitors' phones never appear on your computer; without tracking you only hear when someone complains.

Before you start

Which host logs do you already have (function logs)?

The prompt for this step

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

WHAT I WANT NEXT
See errors that visitors hit (error tracking and logs)

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
Errors that happen on visitors' phones never appear on your computer; without tracking you only hear when someone complains.

DO THESE STEPS, IN THIS ORDER
1. Show me how to read the host's function logs for errors first, before adding any tool.
2. If a tool is useful, recommend one light error tracker, with a free tier note, configured to hide personal data, keys and form contents.
3. Make important failures (payment, sign-in, form, email) log a clear one-line message with a code and no private data.
4. Set up an alert for new kinds of error and a weekly look at the top errors.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- A test error appears in the tracker or logs with enough information to fix it, and no private data.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not log passwords, card data or full personal details.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Show me how to read the host's function logs for errors first, before adding any tool.
If a tool is useful, recommend one light error tracker, with a free tier note, configured to hide personal data, keys and form contents.
Make important failures (payment, sign-in, form, email) log a clear one-line message with a code and no private data.
Set up an alert for new kinds of error and a weekly look at the top errors.

Do not do this

Do not ignore the same error appearing every day.
Do not log passwords, card data or full personal details.

Try another entry