|
Some checks are pending
CI / Build og unit tests (push) Waiting to run
CI / Integration (mcr.microsoft.com/mssql/server:2017-latest) (push) Blocked by required conditions
CI / Integration (mcr.microsoft.com/mssql/server:2019-latest) (push) Blocked by required conditions
CI / Integration (mcr.microsoft.com/mssql/server:2022-latest) (push) Blocked by required conditions
CI / Integration (mcr.microsoft.com/mssql/server:2025-latest) (push) Blocked by required conditions
The hub records when an instance changes build and works out which findings went away within three days of an update and which were still there a week later (version rules excluded). Staff see every effect in the portal; effects seen at three or more customers, resolved more often than not, are served to licensed agents as anonymous counts (rule, major version, build, CU, customers, instances). The agent fetches them every six hours and the web UI shows them on matching findings: 'at 3 customers this went away after updating to CU21'. Data processing documentation covers the aggregation. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E3EExwndy8Z22EK2Qpt6BK |
||
|---|---|---|
| .. | ||
| SQLInsight.Agent.Tests | ||
| SQLInsight.Collectors.Tests | ||
| SQLInsight.Connectivity.Tests | ||
| SQLInsight.Core.Tests | ||
| SQLInsight.IntegrationTests | ||
| SQLInsight.Licensing.Tests | ||
| SQLInsight.Notifications.Tests | ||
| SQLInsight.Rules.Tests | ||
| SQLInsight.Updates.Tests | ||