Removal of legacy analytics in GitGuardian self-hosted

Issued on October 9, 2026

Self-hosted instances that run with in-app analytics disabled still display the legacy analytics pages. These pages are deprecated and will be removed in the 2026.10 release. To keep your analytics dashboards, enable in-app analytics before you upgrade to 2026.10.

What's changing

GitGuardian self-hosted ships two generations of analytics:

• Legacy analytics: the original analytics pages, displayed only when in-app analytics is disabled (inAppAnalytics.enabled: false in Helm, or In-App Analytics turned off in the KOTS Admin Console).
• Advanced Analytics: the current dashboards, powered by the in-app analytics job. They cover Protect, Detect, Remediate, and Prevent, plus the Analytics Overview page that aggregates your KPIs in one place.

Starting with 2026.10, the legacy analytics pages are removed from the product. Advanced Analytics becomes the only analytics experience, so instances that keep in-app analytics disabled will have no analytics dashboards after the upgrade.

Who's affected

• Self-hosted: instances where in-app analytics is disabled, with inAppAnalytics.enabled: false in your Helm values or In-App Analytics turned off in the KOTS Admin Console.

Not affected:

• SaaS workspaces.
• Self-hosted instances that already run in-app analytics. Helm installations have it enabled by default since 2026.5.0, unless you explicitly turned it off.

What you need to do

1. Check that your cluster has the headroom. The in-app analytics job runs once a day and requests 8 GB of memory, with a 12 GB limit. It also increases database usage by 15-20% (at least 5-6 GB). See Advanced Analytics resources for the default job configuration.
2. Enable in-app analytics:
   • Helm: set inAppAnalytics.enabled: true in your values file, or remove the override to fall back to the default. See the Helm values reference.
   • KOTS Admin Console (Embedded Cluster, kURL, or KOTS on an existing cluster): turn on In-App Analytics in the KOTS Admin Console configuration, then deploy.
3. Do it before upgrading to 2026.10. Analytics are computed once a day, so the dashboards can take up to 24 hours to fill after you enable them.

Timeline

• Now: legacy analytics are deprecated. Enable in-app analytics at your convenience on your current version.
• 2026.10: legacy analytics are removed. Instances with in-app analytics disabled no longer have analytics dashboards.

Questions

Reach out to your Customer Success Manager or email us at support@gitguardian.com.