Implementing Error Logging and Health Monitoring

By Neel Vora

This post walks through how I built implementing Error Logging and Health Monitoring, and where it fits in the rest of my work.

Museum kiosks running 12 hours a day taught me that observability isn't optional - if something breaks at 3pm on a Saturday, you need to know immediately.

If you want to treat a portfolio like a real product, observability is not optional.

I added error logging and health monitoring to understand how the app behaves in production.

Client errors

A small ErrorBoundary component captures:

• React render errors
• Event handler exceptions
• Unexpected conditions

These are sent to /api/errors where they are written into Supabase.

Server errors

Server routes wrap logic in try blocks and log structured error messages.

Health check endpoint

I added /api/health, which returns:

• Supabase connectivity
• Database table heartbeat
• Current version hash

Admin viewer

In the admin panel, I built a viewer for:

• Error logs
• Timestamps
• Device information

Why it matters

This demonstrates:

• Production readiness
• Operational thinking
• Real observability patterns

Keep exploring

From here you can:

• Visit /neel-vora for more background about me and my work.
• Browse more posts on the blog.