Skip to main content
Version: 0.4 · current

Synthetic checks

OverviewReviewed October 11, 2026
Applies to:Excubius 0.4Roles: Entity admin, Editor
PlansFree · Pro · EnterpriseDeploymentSelf-hosted

Synthetic checks exercise the paths your users depend on, from the Excubius server inside your network: a web page answers with the right content, its certificate is valid, a name resolves, an application reaches SQL Server through the listener, a report renders. A failing synthetic check means users feel it, even when every server looks healthy.

What it monitors​

AreaChecksWhy it matters
Web endpointsAvailability and response time with the expected status and text; TLS certificate validity; DNS resolution of the hostUsers see an error page, a certificate warning or nothing at all
SQL Server pathsThe availability group listener name resolves from the collector; an application-to-SQL round trip through the listenerApplications connect through the listener, so it must resolve and answer after every failover
Reporting ServicesA report renders through the portal; failures in the report server's execution logReports fail for users while the database engine looks fine
IdentityA domain authentication round trip against Entra Domain Services, over WinRM (experimental)Sign-in failures stop every application that uses the domain
PlatformThe platform's own heartbeat answersOne signal that Excubius itself runs. Register https://<your server>/heartbeat with an external watcher too: the platform must not be the only thing watching itself

The results also appear in the Synthetic checks zone of the Overview. Every check, with its rule, cause and action, is in the reference for synthetic checks.

Before you begin​

  • The module is on. The feature monitoring.synthetics covers this module.
  • Network. The Excubius server reaches the endpoints on 443 or 80, its DNS resolver on 53, and the listeners on the SQL port.

Web endpoints​

  • A web endpoint needs no credential. Only GET and HEAD requests are sent.
  • For a protected endpoint, set the check parameter auth to basic, bearer or ntlm and give the resource a matching credential: HTTP user and password, Bearer token or Windows account.
  • The TLS check reports the days until the certificate expires and fails on an untrusted chain, a name mismatch or a protocol below min_tls (1.2 by default).
  • The DNS check resolves the host with the server's resolver. Set expect_addresses to pin the answer.

Reporting Services​

  • Report render. Add a SQL Server Reporting Services resource with its portal_url and a Windows account credential (DOMAIN\user); the check signs in with NTLM. Without test_report_path it requests <portal_url>/ReportServer, which proves the service is up and sign-in works; with it, it renders that report as CSV. The account needs the Browser role on the report's folder, or on the home folder when you test no report.

  • Portals that require Kerberos only, or Extended Protection set to Require, are not supported. Set Extended Protection to Allow, or use Basic authentication over HTTPS with an HTTP user and password credential and the check parameter auth: basic.

  • Execution log. This T-SQL check reads the report server database (report_server_db, ReportServer by default) on the instance in the resource's host, port and instance. It needs a SQL login: when the resource holds the Windows account, give this check its own credential. Grant the monitoring login read access to the log:

    USE [ReportServer];
    CREATE USER [usr_monitoring] FOR LOGIN [usr_monitoring];
    GRANT SELECT ON dbo.ExecutionLog3 TO [usr_monitoring];

SQL Server paths​

The listener checks run on availability group resources with the same read-only login as the SQL Server module. See Prerequisites for availability groups.

Add a resource​

To test a web endpoint:

  1. Open Resources › Add resource and choose Web endpoint / portal.
  2. Enter the url, for example https://ventas.ciguapa.example/, and optionally expect_status, expect_text and the domain for domain expiry.
  3. Select Create resource, then Test connection on its page.

Listener checks appear on the availability groups that discovery creates. The full wizard: Add a resource.

Next steps​