AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

cloudflare-deploy

Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.

Original source
openai
License
Apache-2.0
Pinned revision
49f948faa9258a0c61caceaf225e179651397431

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read openai--cloudflare-deploy at revision 49f948faa9258a0c61caceaf225e179651397431, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 309

references/analytics-engine/README.md

Cloudflare Workers Analytics Engine Reference

Expert guidance for implementing unlimited-cardinality analytics at scale using Cloudflare Workers Analytics Engine.

What is Analytics Engine?

Time-series analytics database designed for high-cardinality data (millions of unique dimensions). Write data points from Workers, query via SQL API. Use for:

  • Custom user-facing analytics dashboards
  • Usage-based billing & metering
  • Per-customer/per-feature monitoring
  • High-frequency instrumentation without performance impact

Key Capability: Track metrics with unlimited unique values (e.g., millions of user IDs, API keys) without performance degradation.

Core Concepts

| Concept | Description | Example | |---------|-------------|---------| | Dataset | Logical table for related metrics | api_requests, user_events | | Data Point | Single measurement with timestamp | One API request's metrics | | Blobs | String dimensions (max 20) | endpoint, method, status, user_id | | Doubles | Numeric values (max 20) | latency_ms, request_count, bytes | | Indexes | Filtered blobs for efficient queries | customer_id, api_key |

Reading Order

| Task | Start Here | Then Read | |------|------------|-----------| | First-time setup | configuration.md → api.md → patterns.md | | | Writing data | api.md → gotchas.md (sampling) | | | Querying data | api.md (SQL API) → patterns.md (examples) | | | Debugging | gotchas.md → api.md (limits) | | | Optimization | patterns.md (anti-patterns) → gotchas.md | |

When to Use Analytics Engine

Need to track metrics? → Yes
  ↓
Millions of unique dimension values? → Yes
    ↓
  Need real-time queries? → Yes
      ↓
    Use Analytics Engine ✓

Alternative scenarios:
- Low cardinality (<10k unique values) → Workers Analytics (free tier)
- Complex joins/relations → D1 Database
- Logs/debugging → Tail Workers (logpush)
- External tools → Send to external analytics (Datadog, etc.)

Quick Start

  1. Add binding to wrangler.jsonc:
{
  "analytics_engine_datasets": [
    { "binding": "ANALYTICS", "dataset": "my_events" }
  ]
}
  1. Write data points (fire-and-forget, no await):
env.ANALYTICS.writeDataPoint({
  blobs: ["/api/users", "GET", "200"],
  doubles: [145.2, 1],  // latency_ms, count
  indexes: [customerId]
});
  1. Query via SQL API (HTTP):
SELECT blob1, SUM(double2) AS total_requests
FROM my_events
WHERE index1 = 'customer_123'
  AND timestamp >= NOW() - INTERVAL '7' DAY
GROUP BY blob1
ORDER BY total_requests DESC

In This Reference

  • configuration.md - Setup, bindings, TypeScript types, limits
  • api.md - writeDataPoint(), SQL API, query syntax
  • patterns.md - Use cases, examples, anti-patterns
  • gotchas.md - Sampling, index selection, troubleshooting

See Also