From e0791d6e50dbc1eac8d87caccbaafe15f7c41059 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 15 Oct 2026 17:23:38 +0000 Subject: [PATCH] docs(telemetry): count every managed cluster and add the deployment marker Spec 022 Phase 12 (FR-043 to FR-045): reports sum servers and templates over every cluster the panel manages and can reach, the environment covers those clusters, and the extended tier says whether the panel runs on a cluster or standalone. Co-Authored-By: Claude Opus 5.5 (1M context) Signed-off-by: Claude --- src/content/docs/platform-settings-telemetry.mdx | 2 +- src/pages/telemetry.astro | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/docs/platform-settings-telemetry.mdx b/src/content/docs/platform-settings-telemetry.mdx index 592ae1e..74880a7 100644 --- a/src/content/docs/platform-settings-telemetry.mdx +++ b/src/content/docs/platform-settings-telemetry.mdx @@ -48,7 +48,7 @@ Usage telemetry is on by default for new installs and is not a substitute for op On a new install the first admin to sign in sees a notice naming the destination and both tiers; nothing is sent until an admin has seen it. Admin Settings > Telemetry then shows the destination, a preview of the next report, the last attempt, separate switches for the basic and extended tiers, and an install-ID reset. Turning basic off turns extended off with it. -**Basic** sends only the Gameplane version, the GameServer count and the GameTemplate count. **Extended** adds a random install ID, the Kubernetes minor version, a distribution category, CPU architectures and a node-count band, server counts per official module (custom modules are one combined count), feature adoption flags and bands, the database kind, the UI language, a public signing key and the send time. Every value comes from a fixed set or is a number; names, namespaces, hostnames, addresses and player data are never sent. +**Basic** sends only the Gameplane version, the GameServer count and the GameTemplate count, summed over every cluster the panel manages and can reach. **Extended** adds a random install ID, the Kubernetes minor versions, distribution categories, CPU architectures and a node-count band of those clusters, whether the panel runs on a cluster or standalone, server counts per official module (custom modules are one combined count), feature adoption flags and bands, the database kind, the UI language, a public signing key and the send time. Every value comes from a fixed set or is a number; names, namespaces, hostnames, addresses and player data are never sent. What is sent

Two tiers, about once a day, only while an admin has left them on.

    -
  • Basic: exactly version (Gameplane version), servers (number of GameServers), templates (number of GameTemplates).
    • -
  • Extended (adds only the following): a random install ID (a UUID generated on the install, not derived from the cluster, host, network or users); environment: Kubernetes minor version, a distribution category (k3s, rke2, k0s, eks, gke, aks, openshift, microk8s, minikube, kind, doks, talos or other), CPU architectures, and a node-count band (1, 2-3, 4-10, 11-50, 51+); game usage: a server count for each official catalog module plus one combined custom count; feature adoption: wake-on-connect, relay tunnel types (frp, tailscale, playit), packet capture, backups, single sign-on, audit forwarding (each yes/no), a registered-cluster band (1, 2-3, 4-10, 11+), database kind (sqlite or postgres) and UI language; the install's public signing key and the time the report was sent.
    • +
  • Basic: exactly version (Gameplane version), servers (number of GameServers), templates (number of GameTemplates), counted over the local cluster, when there is one, and every registered cluster the panel can reach.
    • +
  • Extended (adds only the following): a random install ID (a UUID generated on the install, not derived from the cluster, host, network or users); environment, over every cluster the panel can reach: Kubernetes minor versions, distribution categories (k3s, rke2, k0s, eks, gke, aks, openshift, microk8s, minikube, kind, doks, talos or other), CPU architectures, a node-count band over all their nodes (1, 2-3, 4-10, 11-50, 51+), and whether the panel runs on a cluster or standalone; game usage: a server count for each official catalog module plus one combined custom count; feature adoption: wake-on-connect, relay tunnel types (frp, tailscale, playit), packet capture, backups, single sign-on, audit forwarding (each yes/no), a registered-cluster band (1, 2-3, 4-10, 11+), database kind (sqlite or postgres) and UI language; the install's public signing key and the time the report was sent.
  • Every extended value comes from a fixed set of categories or bands, or is a number, the install ID, the public key or the send time; anything else is sent as other.