Hosted telemetry

You want upstream latency and error rates for your site, but you don't want to run a collector or a dashboard. The hosted Deco CMS runs one for you.

Telemetry is open source and can go to any OpenTelemetry collector. This page shows how to send it to the hosted Deco CMS instead, and what you get there. Page views are analytics, which is separate: by default, analytics sends to the hosted collector.

Turn it on

Pass your site's ID and token as the telemetry option of createCMS:

const { DECO_SITE: site, DECO_SITE_TOKEN: token } = process.env;
 
export const cms = createCMS({
  blocks,
  content,
  site,                                               // loads releases and drafts
  token,
  telemetry: site && token ? { site, token } : false, // telemetry is separate: site/token above only load releases
});

They're the same values that connect your site for releases and drafts, but telemetry is passed explicitly: the top-level site and token alone never send it. The site && token check keeps telemetry off where the variables aren't set, such as on your machine.

What you get

The hosted Deco CMS collects and shows, for your site, the measurements your site sends: upstream latency, error rates and cache hits per provider, sampled error logs, and traces when you turn them on. Inbound requests and page caches come from your framework's own OpenTelemetry setup, not from Deco CMS.

Settings

What's sent and how often is the same as with any collector: the telemetry section of the CMS block holds the switches and sample rates, and limits in code cap them.