Monitoring Teable with Vigilmon: Health Endpoint, Web UI, API Availability & SSL Alerts

Teable is the open-source, no-code database platform that gives teams a spreadsheet-style interface backed by PostgreSQL. Because Teable is often the central hub for project tracking, CRM data, and team workflows, any downtime means your team loses access to critical shared data. A crashed API server means no record updates. A broken web UI means no one can see or edit data. An expired SSL certificate means browsers block access entirely. Vigilmon gives you external visibility into Teable's health endpoint, web UI availability, API availability, and SSL certificate before your team notices something is wrong.

What You'll Build

• An HTTP monitor on Teable's health endpoint
• An HTTP monitor verifying web UI availability
• An HTTP monitor for API availability
• SSL certificate monitoring for your Teable domain

Prerequisites

• A running Teable instance with a public or network-reachable domain
• HTTPS configured (e.g., https://teable.example.com)
• A free account at vigilmon.online

Step 1: Verify Teable's Health Endpoint

Teable exposes a built-in health check endpoint that reports the status of the application server and its dependencies:

curl https://teable.example.com/api/health

A healthy Teable instance returns HTTP 200 with a JSON response similar to:

{"status":"ok"}

This endpoint confirms the Node.js application server is running, the database connection to PostgreSQL is active, and background services are operational. It requires no authentication and is safe to poll frequently.

Tip: If you've deployed Teable behind a reverse proxy, confirm the /api/health path is not blocked by your proxy configuration. Some setups restrict /api/* routes to specific IP ranges.

Step 2: Create a Vigilmon HTTP Monitor for the Health Endpoint

1. Log in to Vigilmon → Add Monitor → HTTP.
2. URL: https://teable.example.com/api/health.
3. Check interval: 60 seconds.
4. Response timeout: 15 seconds.
5. Expected status: 200.
6. Keyword: ok.
7. Click Save.

This monitor catches:

• Teable server crashes or out-of-memory restarts
• PostgreSQL connectivity failures (Teable requires a healthy database to serve this endpoint)
• Application startup failures after a deployment or update
• Resource exhaustion causing the Node.js process to become unresponsive

Step 3: Monitor Web UI Availability

Teable's web interface is the primary way your team interacts with data. Even if the API backend is healthy, a broken frontend deployment or misconfigured static asset server means users are greeted with blank pages or JavaScript errors.

curl -I https://teable.example.com/

A healthy Teable instance serves HTTP 200 with the application shell containing teable in the HTML title or body.

1. Add Monitor → HTTP.
2. URL: https://teable.example.com/.
3. Check interval: 2 minutes.
4. Expected status: 200.
5. Keyword: teable.
6. Label: Teable Web UI.
7. Click Save.

When the web UI monitor fires but the health endpoint is green, you likely have a frontend asset issue — a failed deploy, a CDN misconfiguration, or a broken build artifact. The backend is alive, but users can't see anything.

Step 4: Monitor API Availability

Teable's REST API powers integrations, automation workflows, and any scripts your team uses to sync data. Monitor a lightweight API route independently to confirm the API layer is functional:

curl https://teable.example.com/api/auth/config

This endpoint returns Teable's authentication configuration (OAuth providers, signup settings) and requires no authentication token. It responds with HTTP 200 and JSON containing keys like allow or providers.

1. Add Monitor → HTTP.
2. URL: https://teable.example.com/api/auth/config.
3. Check interval: 3 minutes.
4. Expected status: 200.
5. Keyword: providers.
6. Label: Teable API.
7. Click Save.

Alternative: If you have a read-only API token, monitor https://teable.example.com/api/space with an Authorization: Bearer <token> header for a richer signal that includes space listing — confirming database reads are working, not just authentication config.

Step 5: Monitor SSL Certificates

Teable relies on HTTPS for all browser access and API calls. An expired certificate blocks every user and every integration simultaneously, with no graceful degradation.

1. Add Monitor → SSL Certificate.
2. Domain: teable.example.com.
3. Alert when expiry is within: 30 days.
4. Alert again: 14 days, 7 days, 3 days, 1 day.
5. Click Save.

A 30-day warning gives you time to renew before any impact. If you're using Let's Encrypt with automatic renewal, an alert at 30 days usually means your ACME client (Certbot, Caddy, or Traefik) failed silently.

Step 6: Configure Alerting

In Vigilmon under Settings → Notifications, configure your alert channels:

| Monitor | Trigger | Action | |---|---|---| | /api/health | Non-200 or keyword missing | Check Teable container logs; verify PostgreSQL connectivity | | Web UI | Non-200 or keyword missing | Check frontend deployment; review reverse proxy config | | API /api/auth/config | Non-200 or keyword missing | Check API routing; inspect Node.js logs for startup errors | | SSL certificate | < 30 days to expiry | Renew certificate; check ACME automation on your reverse proxy |

Alert after: 2 consecutive failures for HTTP monitors to avoid false positives from transient restarts. 1 failure for SSL monitors.

Common Teable Failure Modes and What Vigilmon Catches

| Scenario | Vigilmon monitor | |---|---| | Teable server crash | Health endpoint unreachable; alert within 60 s | | PostgreSQL connection lost | Health endpoint returns non-200; all data access fails | | Frontend deploy fails | Web UI monitor fires; health endpoint stays green | | API server overloaded | API monitor times out; other monitors may stay green | | SSL certificate expires | SSL monitor alerts at 30 days; all browser access blocked | | Reverse proxy misconfiguration | All HTTP monitors fire simultaneously | | Disk full (PostgreSQL WAL) | Health endpoint non-200; database writes fail | | Node.js memory leak | Health endpoint slow or timing out; check container memory |

Teable stores the data your team depends on daily — spreadsheets, project trackers, CRM records, and workflow state. Vigilmon watches the health endpoint, web UI, API availability, and SSL certificate so you know the moment Teable has a problem, before your team opens a ticket wondering why their data is inaccessible.

Start monitoring Teable in under 5 minutes — register free at vigilmon.online.