Operations dashboard

CoreCheck v2

Waiting for first scan

Page not refreshed yet

Next refresh: --
0 Green
0 Action Needed
0 Disabled
0 servers
0 Targets

Add CoreCheck Target

Enter one server plus one exact corecheck endpoint path. This creates one dashboard tile.

Auth Profiles

Store a Keycloak client-credentials profile. The client secret is encrypted by the API before it is saved.

CoreCheck Help

Quick operating notes for reading the dashboard and fixing common failures.

Common Status Codes

401 Unauthorized
The API did not accept the request as authenticated. Check the tile auth profile, token URL, Keycloak realm, client id/secret, and whether the deployed API expects a different auth server.
403 Forbidden
The token was accepted, but the service account does not have the required role. Add the expected realm role, such as db_read or file_read, to the scanner service account in the API's realm.
404 Not Found
The server responded, but the endpoint path was not found. Check the IIS application folder plus controller route, for example Folder/Controller/corecheck.
500 Server Error
The endpoint was found, but the application failed. Check the app pool, .NET hosting bundle/runtime, appsettings environment, database access, logs, and missing files.

Environment Icons

The icon on each tile comes from the latest CoreCheck JSON message for that API. CoreCheck reads environmentvariable first, then environment. If the tile is disabled or the value is missing, unreadable, or unrecognized, the tile shows Unknown.

Experimental
Demo, sandbox, or experimental deployments.
Development
Developer or team-development deployments.
Staging
Pre-production validation deployments.
Production
Production/customer-facing deployments.
Unknown
No reliable environment was reported. This can indicate a disabled tile, failed check, non-JSON response, or missing environment field.

Database Model

CoreCheck v2 uses one central SQL Server database right now. The active database lives on products.coredata.ca, and additional CoreCheck API deployments connect back to it.

For this stage, products.coredata.ca and aicoredev2.coredata.ca show the same source-of-truth records. Remote SQL access is restricted by firewall rules and uses a SQL login stored as server configuration, not in the web code.

Scan, Refresh, and Automation

Refresh
Reloads the latest saved dashboard data from CoreCheck API. It does not call the monitored APIs.
Scan Now
Asks CoreCheck API to call enabled corecheck endpoints and save new results to SQL.
Scheduled scans
The active scheduler runs from the primary products deployment every 5 minutes. It performs a full scan of enabled targets every 30 minutes. Secondary deployments can display and edit data, but should not run a scheduler until scan locking is implemented.
Retry behavior
Green targets wait for the 30-minute macro cycle. Failed targets are retried every 5 minutes, with a 60-second delay between failed checks on the same server to reduce pressure during outages.

Stage-1 Uptime

The uptime and downtime values on each server bar are simple accumulators for now. They are not yet calculated from a complete scan history.

When the scheduled 30-minute full scan sees every enabled tile on a server green, CoreCheck adds 30 minutes to that server's uptime. When the 5-minute retry scan still finds action-needed tiles on a server, CoreCheck adds 5 minutes to downtime. Counters since shows the start of the current accumulator window. Reset clears both counters for that server and moves that start time to the reset time.