System health

Admins only: This tab is for site administrators.

The Health tab runs Kenseme’s health checks when you open it and shows the result, along with details about the server instance that answered.

In the app: Settings › System Administration › Health tab

[screenshot]

System health¶

Overall Status sums up every check as Healthy, Degraded, or Unhealthy. The grid below lists each check:

Column	Meaning
Service	The check’s name.
Status	Healthy, Degraded, or Unhealthy.
Response Time	How long the check took.
Description	The check’s message, including the error when it fails.

The checks are:

Service	What it checks
BlazeDatabase	The main application database, where every organization’s content lives.
InsightsDatabase	The database that records AI usage and application logs, including the errors on the Errors tab.
HangfireDatabase	The database that stores the background job queue.
AzureCommunicationServices	The email service that sends invitations and notifications.

Click Refresh to run the checks again.

System information¶

The System Information card describes the server instance you’re connected to: Build Version, Environment, Machine Name, Process ID, Processor Count, Working Set (memory in use), and Server Time (UTC).

Note: Kenseme can run on more than one server. Health checks and system information come from whichever instance served your page, so another instance can differ.

When something is unhealthy¶

• Read the Description for the immediate cause.
• If AzureCommunicationServices fails, invitations and notices won’t send. Organizations can still copy invitation links by hand, and failed emails can be resent later from their Outgoing Emails tab.
• If a database check fails, check the Errors tab for matching errors and the Background Jobs tab for jobs that stopped moving.

Tip: A check is a snapshot. Passing now doesn’t mean the last hour was clean; use your monitoring dashboards for trends.

Related¶

• Errors
• Site-wide background jobs
• System administration