The Public Telemetry Dashboard

Everything <AppName /> measures, published as anonymous counts anyone can read.

Applies To

Every liveworkspace app

The telemetry dashboard is a public page, headed Telemetry, in the open, that shows everything liveknowledge measures. It lives at liveworkspace.app, one dashboard for every liveworkspace app: the link opens it with the app's own address picked, and All apps shows every app's events together. There is no sign-in and nothing hidden behind it: the page reads the same anonymous counts the project itself uses to decide what to build next. This article walks through what it shows and how to read it. For what an event is and how to switch it off, see What We Collect.

What the Numbers Are Made Of

Every number on the dashboard is a count of small events, each made of just three fields: a category, an action and an optional preset type, such as Element, Added, Square. No event carries a user id, an IP address, a knowledgebase or anything you typed, so the dashboard can only ever show totals, never a person or a path through the product.

Events are deleted automatically after 60 days. The dashboard's longest window is 30 days, so what you see is recent trend data rather than a permanent archive.

Most events come from browsers that have telemetry switched on. A few are counted by the server itself, because only the server can see them once: a sign-up or sign-in, a share-link visitor's first visit to a knowledgebase, a knowledgebase used by several people at once, an email sent, and a server error. They are the same three anonymous fields, and they appear in the same charts.

The counts are refreshed a few minutes at a time, so a brand-new event can take a short while to show.

Choosing a Window

At the top, three cards set the time window for the whole page: Today, Last 7 days and Last 30 days, each with its total number of events. The page opens on Last 7 days. Pick a card and every view below counts over that window.

The windows are whole calendar days in UTC: Today is since midnight UTC, Last 7 days is today and the six days before, and Last 30 days is today and the 29 days before. Under the cards, Daily Volume, Last 30 Days (UTC) draws one line across the whole month, with the span of the chosen window highlighted, so a card's total always matches its highlighted stretch of the line.

The window cards over the daily trend line, the view tabs with Dashboard open, and the first cards of the Visitors group.

The Views

The dashboard is one page for every app, so its views are one component: pick an app with the chips under the heading (All Apps, or one app by its logo) and the same row of tabs appears over that app's own numbers. Dashboard and Search stand on their own at the left; every other view is a closer look at one area, in a bar titled Detail. There is a tab for each area, so the bar wraps onto further rows on a wide screen and scrolls sideways on a phone. Picking another app keeps the window you chose.

  • Dashboard: the overview, and where the page opens. It leads with At a glance, then groups a fixed list of charts by the question they answer: Visitors, Content, Features, Collaboration, Connections, and Health & support. Each card shows the window's count with a line for the last 30 days, and a stack opens into the cards it combines. A stack's See also link opens the Detail tab that breaks it down further.
  • Editing: the tools that organise work, then formatting controls, export formats and dialogs.
  • Palette: what people add, most to least used.
  • Modes: the modes people switch into and the options they set inside them.
  • Look & Feel: which templates and themes get picked.
  • Settings: how often each setting is changed, and which Settings categories people open.
  • The app's people tools (see below).
  • Community: what people do with what they share on the app's Community page, and why posts get reported.
  • Connections: API tokens and the changes AI tools make.
  • Pages: the most-viewed pages across every app, and each app's own top ten. Ids never leave the browser, so every knowledgebase counts as one page.
  • Help: help centre reads and article feedback, and the articles opened from inside the editor.
  • Tours & Prompts: how far people get through each guided tour, and how they answer the one-off prompts.
  • Exceptions: what failed and where, counted only as a short code such as a status and the request or area, never an error message or stack. An empty tab here is the goal.
  • Timings and Web Vitals: how fast it all is (see below).
  • Search: find any one metric, by typing or by clicking through a word cloud of categories, actions and types, and see just that metric charted over 30 days.

All Apps has the same shape, but the apps keep their own vocabularies, so it shows only what they share. Its Dashboard adds every app up in six cards, then gives each app a card under its logo that opens the app's own dashboard. Its Detail tabs are Events by App and Visitors & Accounts (each app set against the others), Project Kits (the kits liveworkspace.app starts), Forum Checks and the Busiest Events, added up across apps.

Timings and Core Web Vitals

Browsers never send an exact time, only the range a timing fell in (such as "under one second"). So every number on the Timings and Web Vitals tabs is an estimate within its range.

The Timings tab has one card each for Load (opening a knowledgebase), Warm Paint (reopening a knowledgebase this browser has opened before, until its last seen copy is on screen), Tab Switch, Save, Live Connect and Live Reconnect. Each card leads with the p75 (three timings in four were at least this quick), shows the Median and p95 beside it, draws how many timings fell in each range, and plots each day's p75 across the last 30 days. A card with fewer than 20 timings in the window says it has too few to read a percentile, rather than showing a misleading number.

Every app has both tabs, and the load card is named for what the app opens.

The Web Vitals tab gives one card per part of liveknowledge (Marketing, Live, Help, Dashboard and Community) with the 75th percentile of three measures, each rated Good, Needs Work or Poor against Google's thresholds:

MeasureWhat it tracks
LCPHow long the main content took to show
INPHow quickly the page answered a click, tap or key
CLSHow much the page jumped around while it loaded
How this works in 5 other apps

Was this article helpful?

Still need help?

Try Troubleshooting, or tell us what you were trying to do.

Contact us