June–October 2026: Network Tracker, Alert Investigations, and a Public Demo
This update covers the releases since the May changelog. The biggest additions are operational: a public demo, the Network Tracker, and a complete alert investigation loop.
Try it before you connect a server
ShardAnalytics now has a live public demo that runs on generated sample data. Explore the Command Center, Players, Payments, Custom Dashboards, Alerts, Logs, Audit Logs, and the Network Tracker without creating an account.
ShardAnalytics is also free during the open beta. Every feature is included, no credit card is required, and subscription plans will be announced after the beta. Teams that join now keep free access while the beta runs.
Network Tracker
A new Network Tracker gives your network context beyond its own numbers:
- Network catalog: current, peak, and record player counts, uptime ratio, sample coverage, and freshness for tracked networks.
- Benchmarks: comparison sets, ranking against peers, player-count comparison charts, and external network search.
- Network presence: organization-level presence tracking across the fleet.
The Network Tracker is in beta and free during the open beta.
Network plugin inventory
- Inventory and history: see which plugins and versions run across every server, with version history per server. Easily check which servers have outdated versions.
- Fuzzy search: find plugins and history entries quickly across large networks.
- Per-server views: confirm what is installed on one server when troubleshooting an add-on integration.
Alert investigations
- Investigation loop: alerts now open into an investigation with the metric summary, correlated signals, related logs, and a timeline of what changed.
- Bulk actions: acknowledge or resolve alert evaluations in bulk from the alerts list.
- Alert rules toolbar: select and act on multiple rules at once.
Server observability
- Network interfaces: RX/TX per interface alongside player-facing latency.
- Pipeline health: batches sent and failed, data points, queue depth, authentication blocks, and connection failures.
- GC event analysis: duration and time histograms, a data table, filter bar, dynamic colour mapping, and detailed tooltips.
- Memory pools: multiple pool names supported with per-pool usage.
- Metrics API: aggregation and options endpoints for JVM, pipeline health, network interfaces, and GC events.
Payments
Building on May’s payments release:
- Server payments overview: revenue views scoped to a single server.
- Provider mapping: map store destinations to ShardAnalytics servers so revenue is attributed correctly.
- Richer transactions: destination formatting and package details on transaction rows.
- Integration notices: clearer states when a payment integration needs attention.
Player purchases
Player profiles now include a purchases section, so a player’s store history sits next to their activity, gameplay, and session data.
Operations insights and tours
- Periodic insights: the Operations Command Center surfaces periodic insights with continuation context.
- Investigation sheet: open an insight to inspect its evidence, acknowledge it, or leave feedback.
- Guided setup and tours: contextual product tours walk new users through setup and the main analytics surfaces.
Servers
- Server tags: tag servers for easier filtering and organization.
Organization terminology and onboarding
- Simpler onboarding: the onboarding flow creates an organization directly; the separate node creation step is gone.
- Unified sidebar: one navigation with a pinned server workspace.
Logs and filtering
- Multi-server logs: select several servers at once when searching logs.
- Consistent filters: shared filter form primitives across analytics, payments, and logs.
Interface
- Mobile navigation: improved navigation and UI components on small screens.
- Interactive geomaps: shared interactive maps with dark-mode contrast and geo distribution tooltips.
- Faster dashboards: shared queries and progressive refresh.
Documentation
The documentation has been rebuilt around how the platform is actually used: getting started, the Minecraft plugin, data and events, dashboards and funnels, players, stores, campaigns, operations, and team settings, with a glossary for retention, payment, and attribution definitions.