{
  "version": "2",
  "id": "https://freelancenews.online/news/cloudflare-adds-workers-observability-logs-and-traces-to-custom-b42e7973",
  "title": "Cloudflare adds Workers Observability logs and traces to Custom Dashboards",
  "summary": "Two new datasets let account holders chart Worker telemetry — including invocations, log levels, errors, CPU and wall time, span counts and durations — alongside HTTP traffic and security events, with the per-account dashboard cap raised to 100.",
  "body": "Cloudflare has made Workers Observability data a chartable source inside Custom Dashboards, per a changelog entry on its developer documentation site. The change adds two datasets — Workers Observability — Logs and Workers Observability — Traces (OTel) — that can be used to build Custom Dashboards charts from Workers telemetry.\n\nThe changelog frames consolidation as the objective. Its statements indicate that account holders can now position Worker telemetry next to HTTP traffic, security events and other analytics datasets. The telemetry concerned spans several signal types: how often Workers are invoked, what log levels appear, how many errors occur, how much CPU and wall time is consumed, how many spans are recorded, and how long those spans last. Put differently, Worker-level telemetry no longer occupies a view of its own; it joins network and security analytics as one more series on a shared dashboard surface.\n\nCloudflare illustrates an intended workflow with a concrete case. Suppose someone wanted Worker error rates, WAF blocks and request volume displayed together; they could filter all three by time range and then examine whether an error spike coincides with a shift in traffic. Across datasets that formerly resided in separate locations, that amounts to a correlation workflow. Automatic root-cause analysis is not something the changelog says these dashboards carry out.\n\nAvailability is tied to existing Workers features rather than to a new subscription. The changelog states the datasets are available for every Worker in an account that has Workers Logs or Workers Traces turned on. That means the prerequisite is an existing observability setting on the Worker itself, not a separate opt-in for the dashboard datasets.\n\nAlongside the datasets, Cloudflare raised a quota: Custom Dashboards now allow up to 100 dashboards for every account. The changelog presents this as a change to the existing limit, though it does not state what the previous cap was, so the size of the increase cannot be established from the supplied text.\n\nThe changelog entry is dated 2026-10-02 in its URL slug, and the supplied source timestamp corresponds to that date. The evidence does not include a separate announcement, pricing page, or migration note, so the release is documented here only through the changelog itself.\n\nFor freelancers and small studios running client work on Workers, the practical effect is that Worker error rates and latency signals can be placed on the same time axis as the traffic and security data they already watch. When a client reports intermittent failures, a single filtered view can show whether Worker errors moved at the same moment as a traffic shift or a WAF action, instead of requiring a manual cross-reference between tools.\n\nThat said, the value depends on telemetry already being switched on. If Workers Logs or Workers Traces are off for a given Worker, the changelog indicates the datasets are not available for it — so the first step for anyone adopting this is auditing which Workers in an account actually have those features enabled.\n\nThere are also open questions the changelog does not answer. It does not describe retention windows for the underlying logs and traces, query cost or billing implications for charting them, cardinality limits on the new datasets, or whether the datasets behave differently across Workers plans. None of that is addressed in the supplied text, and it should not be assumed either way.\n\nThe raised dashboard limit is the kind of change that matters most to accounts managing several clients or environments. A cap of 100 dashboards per account is a stated figure; whether that is generous or tight depends on how an account is organised, and the changelog offers no guidance on structuring dashboards per project or per client.\n\nIt is worth separating what is documented from what is implied. The changelog documents the existence of two datasets, the fields they can chart, the prerequisite of Workers Logs or Workers Traces being on, and the new 100-dashboard ceiling. It does not document performance characteristics, data freshness, or how the OTel traces dataset maps to specific span attributes beyond span counts and durations.\n\nFor developers who maintain observability for client applications, the sensible reading is that this reduces context-switching between Worker telemetry and edge analytics, but does not remove the need to configure logging and tracing deliberately. Teams that have treated Workers Logs as optional may find the new datasets give them a reason to revisit that decision.\n\nThe changelog points readers to documentation on using Workers Observability data in Custom Dashboards for setup details. Those setup steps are not included in the supplied evidence, so anyone planning to build charts should consult that documentation rather than assume a configuration path.\n\nOverall, this is an incremental but concrete platform change: two named datasets, a stated availability condition, and a numeric quota increase. Its usefulness for freelance and small-team workflows rests on whether the Workers in question already emit logs or traces, and on how much of an account's monitoring already lives in Cloudflare's dashboard tooling.",
  "category": "dev",
  "language": "en",
  "datePublished": "2026-10-05T03:18:18.800Z",
  "dateModified": "2026-10-05T03:18:18.800Z",
  "eventDate": "2026-10-02",
  "sourcePublicationDate": "2026-10-02T00:00:00.000Z",
  "source": {
    "name": "developers.cloudflare.com",
    "url": "https://developers.cloudflare.com/changelog/post/2026-10-02-workers-observability-in-custom-dashboards/",
    "kind": "official-publisher"
  },
  "practicalImpact": "Editorial interpretation: freelancers and small teams running client workloads on Workers can put Worker error rates and latency on the same filtered timeline as traffic and WAF events, which shortens the manual cross-referencing step when diagnosing intermittent failures — provided Workers Logs or Workers Traces are already enabled for those Workers.",
  "limitations": "The evidence is a single changelog entry. It does not state the previous dashboard limit, retention windows, query or billing costs, cardinality limits, plan differences, or setup steps, and it does not describe how the OTel traces dataset maps to specific span attributes beyond span counts and durations. No independent verification or testing is claimed.",
  "keyPoints": [
    "Cloudflare added two Custom Dashboards datasets: Workers Observability — Logs and Workers Observability — Traces (OTel).",
    "The datasets can chart Worker invocations, log levels, errors, CPU and wall time, span counts and durations alongside HTTP traffic and security events.",
    "Availability requires Workers Logs or Workers Traces to be turned on for the Worker.",
    "Custom Dashboards now allow up to 100 dashboards per account, per the changelog."
  ],
  "review": {
    "status": "source-reviewed",
    "checkedAt": "2026-10-05T03:18:18.800Z",
    "method": "Automated comparison against retrieved source text; not independent fact-checking.",
    "correctionNote": null
  },
  "sources": [
    {
      "id": 1,
      "url": "https://developers.cloudflare.com/changelog/post/2026-10-02-workers-observability-in-custom-dashboards/",
      "publisher": "developers.cloudflare.com",
      "title": "Changelog",
      "publishedAt": 1790899200000,
      "fetchedAt": 1791170271323,
      "hash": "e8f532ffc5afa5f72d247d6e246a235a5e624328591c94782cc545042944b78f",
      "kind": "official-publisher"
    }
  ],
  "claims": [
    {
      "claim": "Cloudflare introduced two Custom Dashboards datasets for Workers Observability data: logs and OTel traces.",
      "source": 1,
      "id": "claim-1",
      "url": "https://freelancenews.online/news/cloudflare-adds-workers-observability-logs-and-traces-to-custom-b42e7973#claim-1"
    },
    {
      "claim": "The datasets support charting Worker invocations, log levels, errors, CPU and wall time, span counts and durations.",
      "source": 1,
      "id": "claim-2",
      "url": "https://freelancenews.online/news/cloudflare-adds-workers-observability-logs-and-traces-to-custom-b42e7973#claim-2"
    },
    {
      "claim": "The datasets are available for every Worker in an account that has Workers Logs or Workers Traces turned on.",
      "source": 1,
      "id": "claim-3",
      "url": "https://freelancenews.online/news/cloudflare-adds-workers-observability-logs-and-traces-to-custom-b42e7973#claim-3"
    },
    {
      "claim": "Custom Dashboards now allow up to 100 dashboards per account.",
      "source": 1,
      "id": "claim-4",
      "url": "https://freelancenews.online/news/cloudflare-adds-workers-observability-logs-and-traces-to-custom-b42e7973#claim-4"
    },
    {
      "claim": "Cloudflare describes combining request volume, WAF blocks and Worker error rates in one filtered view to check whether error spikes align with traffic changes.",
      "source": 1,
      "id": "claim-5",
      "url": "https://freelancenews.online/news/cloudflare-adds-workers-observability-logs-and-traces-to-custom-b42e7973#claim-5"
    }
  ],
  "formats": {
    "html": "https://freelancenews.online/news/cloudflare-adds-workers-observability-logs-and-traces-to-custom-b42e7973",
    "markdown": "https://freelancenews.online/news/cloudflare-adds-workers-observability-logs-and-traces-to-custom-b42e7973.md",
    "json": "https://freelancenews.online/news/cloudflare-adds-workers-observability-logs-and-traces-to-custom-b42e7973.json"
  }
}