Monitoring

<% if (forbidden) { %>
Your role does not have permission to view monitoring data.
<% } else { %> <% if (checkResult) { %>
<%= checkResult.message %>
<% } %>

Service Health

<% for (const s of services) { %>

<%= s.service %>

<%= s.status %>

Latency: <%= s.latencyMs != null ? s.latencyMs + 'ms' : '—' %>

24h uptime: <%= s.uptimePercent24h != null ? s.uptimePercent24h + '%' : '—' %>

<% } %>

Recent Background Job Runs

tenant-api's own scheduled jobs — reminder emails, invoice-overdue sweeps, recurring invoices, email sync, and the rest of its cron schedule (see backend/jobs/scheduler.js) — not this admin console's health checks. Every job writes its own run here through a shared wrapper the moment it starts and finishes, so this is a live log, not a snapshot: "running" means still in progress right now.

<% for (const j of jobRuns) { %> <% } %> <% if (!jobRuns.length) { %><% } %>
JobStatusStartedDurationError
<%= j.job_name %> <%= j.status %> <%= new Date(j.started_at).toLocaleString() %> <%= j.duration_ms != null ? j.duration_ms + 'ms' : '—' %> <%= j.error_message || '' %>
No job runs recorded yet.

Deployments

Detected automatically — each service reports its own version and commit on its health endpoint, and a new row appears here the moment a health check (manual or scheduled) sees that change. No one needs to remember to log a deploy by hand.

<% for (const d of deployments) { %> <% } %> <% if (!deployments.length) { %><% } %>
ServiceVersionStatusRecorded ByWhen
<%= d.service_name %> <%= d.version %><% if (d.commit_sha) { %> @<%= d.commit_sha %><% } %> <%= d.status %> <%= d.deployed_by %> <%= new Date(d.deployed_at).toLocaleString() %> <% if (d.status === 'succeeded' && !d.rollback_of) { %>
<% } %>
No deployments detected yet — run a health check once each service is up.

Database Migrations (tenant-api)

Read-only view of every migration file on tenant-api's disk cross-referenced against its knex_migrations table. Moved here from the firm-facing Settings page — schema/migration state is shared-backend infrastructure, not something any single firm's admin should see or act on. Migrations themselves are still applied manually via npm run migrate, never from this UI.

<% if (migrationsSummary) { %>

Total

<%= migrationsSummary.total %>

Applied

<%= migrationsSummary.applied %>

Pending

<%= migrationsSummary.pending %>

Current Batch

<%= migrationsSummary.currentBatch %>

Last Applied

<%= migrationsSummary.lastAppliedAt ? new Date(migrationsSummary.lastAppliedAt).toLocaleString() : '—' %>

<% } %> <% if (migrationsOrphaned && migrationsOrphaned.length) { %>
<%= migrationsOrphaned.length %> migration(s) recorded as applied whose file no longer exists on disk — possible drift: <%= migrationsOrphaned.map(o => o.name).join(', ') %>
<% } %> <% for (const m of migrations) { %> <% } %> <% if (!migrations.length) { %><% } %>
MigrationStatusBatchApplied
<%= m.name %> <%= m.status %> <%= m.batch != null ? m.batch : '—' %> <%= m.appliedAt ? new Date(m.appliedAt).toLocaleString() : '—' %>
No migration files found.
<% } %>