Cloudflare Observability and Admin Docs
Official Cloudflare developer docs fetched from developers.cloudflare.com, focused on analytics, logging, operations, account administration, IaC, and general docs.
Hard Rules
- MUST search
references/ before giving Logpush, analytics, billing, Terraform/Pulumi, account resource, or support guidance.
- MUST distinguish observability/admin docs from product-specific runtime/security/networking docs; route to focused skills when the product family is known.
- NEVER invent dataset names, Logpush destination config, analytics API fields, Terraform resource names, or billing/support behavior.
Fast Lookup
rg -n "Logpush|Logs|Analytics|Radar|dataset|Log Explorer" skills/cloudflare-observability-admin/references
rg -n "Terraform|Pulumi|account|resource|billing|support" skills/cloudflare-observability-admin/references
rg -n "learning path|reference architecture|migration|fundamentals" skills/cloudflare-observability-admin/references
Reference Map
references/analytics/, logs/, log-explorer.md, radar/ — observability products.references/billing/, support/, notifications/ — account administration.references/terraform/, pulumi/ — infrastructure as code.references/fundamentals/, learning-paths/, reference-architecture/ — general docs and guidance.references/use-cases/, migration-guides/, data-localization/ — cross-product guidance.
1---2name: cloudflare-observability-admin3description: Use when working with Cloudflare observability and account administration: Analytics, Logs, Logpush, Log Explorer, Radar, notifications, billing, support, Terraform/Pulumi, fundamentals, learning paths, reference architectures, account resources, or admin docs.4---56# Cloudflare Observability and Admin Docs78Official Cloudflare developer docs fetched from [developers.cloudflare.com](https://developers.cloudflare.com), focused on analytics, logging, operations, account administration, IaC, and general docs.910## Hard Rules1112- MUST search `references/` before giving Logpush, analytics, billing, Terraform/Pulumi, account resource, or support guidance.13- MUST distinguish observability/admin docs from product-specific runtime/security/networking docs; route to focused skills when the product family is known.14- NEVER invent dataset names, Logpush destination config, analytics API fields, Terraform resource names, or billing/support behavior.1516## Fast Lookup1718```bash19rg -n "Logpush|Logs|Analytics|Radar|dataset|Log Explorer" skills/cloudflare-observability-admin/references20rg -n "Terraform|Pulumi|account|resource|billing|support" skills/cloudflare-observability-admin/references21rg -n "learning path|reference architecture|migration|fundamentals" skills/cloudflare-observability-admin/references22```2324## Reference Map2526- `references/analytics/`, `logs/`, `log-explorer.md`, `radar/` — observability products.27- `references/billing/`, `support/`, `notifications/` — account administration.28- `references/terraform/`, `pulumi/` — infrastructure as code.29- `references/fundamentals/`, `learning-paths/`, `reference-architecture/` — general docs and guidance.30- `references/use-cases/`, `migration-guides/`, `data-localization/` — cross-product guidance.
wenerme