How to Monitor Your Qwik Application with Vigilmon

How to Monitor Your Qwik Application with Vigilmon

Qwik's resumability model changes how JavaScript loads, but your uptime monitoring needs are the same as any other web app. This guide shows you how to add Vigilmon uptime monitoring to a Qwik application.

Why Monitor a Qwik App?

Qwik apps are served from edge runtimes or Node.js servers. Whether you're running qwik-city on Cloudflare Workers, AWS Lambda, or a traditional server, you need to know when:

• Your server is down or timing out
• API routes return 500 errors
• SSL certificates expire
• Response times degrade

Vigilmon handles all of this with zero code changes.

Setting Up Your First Monitor

1. Sign up at vigilmon.online
2. Click Add Monitor
3. Enter your Qwik app URL (e.g., https://myapp.com)
4. Set check interval to 1 minute
5. Add your email or Slack webhook for alerts

Vigilmon will immediately start checking your app every minute from multiple regions.

Monitoring Qwik City API Routes

Qwik City supports server-side routes in src/routes. If you have an API route like /api/health, monitor it directly:

// src/routes/api/health/index.ts
import type { RequestHandler } from '@builder.io/qwik-city';

export const onGet: RequestHandler = async ({ json }) => {
  json(200, {
    status: 'ok',
    timestamp: new Date().toISOString(),
  });
};

Then add a monitor for https://yourapp.com/api/health with:

• Expected status: 200
• Keyword check: "status":"ok"
• Timeout: 10 seconds

Monitoring Qwik on Cloudflare Workers

If you deploy Qwik City to Cloudflare Workers, set up monitoring with these considerations:

• Workers have a 50ms CPU time limit on the free tier — if your app hits this, requests fail silently
• Monitor cold start latency by checking the cf-ray header presence
• Use Vigilmon's response time alerts to catch edge performance issues

Set a response time alert threshold of 2 seconds. If a Worker cold start pushes beyond that, you'll know immediately.

Multi-Region Checks for Edge Deployments

Qwik's frequent deployment to edge runtimes means regional issues matter more. Vigilmon checks from multiple regions including:

• US East / US West
• Europe (Frankfurt)
• Asia Pacific

A Cloudflare Worker that's broken in Asia but fine in the US will show up as a regional failure in Vigilmon's dashboard.

SSL Monitoring

Qwik apps always run on HTTPS. Vigilmon automatically monitors your SSL certificate and alerts you:

• 30 days before expiry
• 14 days before expiry
• 7 days before expiry

No configuration needed — just add your HTTPS URL.

Status Page for Your Users

With Vigilmon, you can create a public status page at status.yourapp.com that shows:

• Current uptime across all monitors
• Historical uptime (30/60/90 days)
• Active incidents with updates

This is especially useful for Qwik apps that serve as backends for other services.

Alert Channels

Vigilmon supports multiple alert channels:

• Email — default, no setup needed
• Slack — paste your webhook URL
• Discord — paste your webhook URL
• PagerDuty — for on-call rotation
• Webhooks — for custom integrations

Quick Summary

Feature	Vigilmon
Check interval	1 minute
Multi-region	Yes
SSL monitoring	Yes
Status pages	Yes
Keyword checks	Yes
Free tier	Yes

Vigilmon's free tier covers 5 monitors with 5-minute checks — enough to get started with your Qwik app. Upgrade when you need 1-minute checks or more monitors.

---

Start monitoring your Qwik application at vigilmon.online.