[Workers] Clarify observability pricing

[WalshyDev]

Summary

• Clarifies that Workers Logs pricing applies to persisted/queryable log events stored by Cloudflare.
• Clarifies that Workers Trace Events Logpush pricing applies to exported events.
• Documents that using both is additive where both overage rates apply.

Validation

• git diff --check origin/production...HEAD
• Targeted pricing content assertions

Full docs validation was not run in this sandbox because it has Node 22 and no pnpm/corepack, while this repo requires Node 24.

[github-actions]

This PR requires additional review attention because it affects the following areas:

Partials

This PR updates partial files, which are pieces of content used across multiple files in our Render component.

• workers/workers_logs_pricing - view affected files

[github-actions]

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern	Owners
/src/content/docs/workers/	@cloudflare/workers-docs, @GregBrimble, @irvinebroque, @mikenomitch, @korinne, @WalshyDev, @cloudflare/deploy-config, @cloudflare/product-owners, @cloudflare/wrangler, @MattieTK, @cloudflare/dev-plat-leads, @vy-ton
/src/content/partials/workers/	@cloudflare/workers-docs, @GregBrimble, @irvinebroque, @mikenomitch, @WalshyDev, @cloudflare/deploy-config, @cloudflare/product-owners, @cloudflare/wrangler, @MattieTK, @vy-ton

[ask-bonk]

Here is my review of PR #31428.

---

Labels

workers documentation

---

Summary

This PR improves the clarity of Workers observability pricing by distinguishing between Workers Logs (persisted/queryable log events) and Workers Trace Events Logpush (exported events). It:

• Renames the section from "Workers Logpush" to "Workers Trace Events Logpush" for precision.
• Updates table headers from "Log Events Written" → "Persisted log events" and "Requests" → "Exported Workers Trace Events".
• Adds explicit sentences explaining that the two services are billed independently.
• Documents the additive overage rate: $0.60 + $0.05 = $0.65 per million events that are both persisted and exported.

---

Validation results

• pnpm run check – ✅ Passed (0 errors, 0 new warnings).
• pnpm exec prettier --check src/content/partials/workers/workers_logs_pricing.mdx – ✅ Passed.
• pnpm exec prettier --check src/content/docs/workers/platform/pricing.mdx – ⚠️ Fails, but on pre-existing table-alignment formatting in the Workers usage-model table (lines ~30), not on any lines touched by this PR. The author did not introduce new formatting issues.

Note: I was able to run these checks successfully in this environment (Node v24.16.0 / pnpm 11.6.0).

---

Review: Approved with minor nits

The changes are accurate, consistent with repo conventions, and materially improve clarity. I have two minor wording suggestions for maintainers to consider:

1. Redundant / ambiguous clause in additive-pricing sentences

Both paragraphs repeat the phrase "where both overage rates apply", which is slightly redundant because the preceding clause already establishes the condition (events are both persisted and exported).

src/content/docs/workers/platform/pricing.mdx (line 142)

- If an event is both persisted by Workers Logs and exported by Workers Trace Events Logpush, the combined overage rate is $0.65 per million events where both overage rates apply.
+ If an event is both persisted by Workers Logs and exported by Workers Trace Events Logpush, the combined overage rate is $0.65 per million such events.

src/content/docs/workers/platform/pricing.mdx (line 161)

- If you both export events with Workers Trace Events Logpush and persist logs with Workers Logs, the combined overage rate is $0.65 per million events where both overage rates apply.
+ If you both export events with Workers Trace Events Logpush and persist logs with Workers Logs, the combined overage rate is $0.65 per million events that are both persisted and exported.

2. Optional: Deduplicate the additive-pricing paragraph

The same additive-pricing explanation appears after both the Workers Logs section and the Workers Trace Events Logpush section. This is helpful for readers who land on only one section, but if the docs team prefers a single source of truth, it could be reduced to one note/callout and a cross-reference. Not a blocker.

---

Other observations

• Unused Markdown import in the partial – this is actually consistent with other partials in src/content/partials/workers/ (e.g., kv_pricing.mdx), so it appears to be a repo convention and does not need cleanup.
• Frontmatter empty-object pattern {} in the partial is also standard across the codebase.
• No unescaped MDX characters, no broken internal links, and no frontmatter issues detected.

Overall, this is a clean, focused docs improvement. LGTM once the author/maintainer decides on the wording nits above.

github run

[github-actions]

Preview URL: https://85d7cbb5.preview.developers.cloudflare.com
Preview Branch URL: https://walshy-workers-observability-pricing.preview.developers.cloudflare.com

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/workers/platform/pricing/	https://walshy-workers-observability-pricing.preview.developers.cloudflare.com/workers/platform/pricing/

[irvinebroque]

/bonk update this PR to make @nevikashah codeowner of the workers observability partial that changed

[ask-bonk]

Done. I added @nevikashah as a codeowner for src/content/partials/workers/workers_logs_pricing.mdx in .github/CODEOWNERS:

+ /src/content/partials/workers/workers_logs_pricing.mdx @irvinebroque @mikenomitch @nevikashah @cloudflare/product-owners @vy-ton

The new entry shares the same owner list as the existing /src/content/docs/workers/observability/ line so that observability docs and this partial are aligned.

github run