// AI Platform Drift

Cloudflare Audit Logs v2 now captures GET request view actions

Cloudflare developer changelog · published 2026-10-15 11:33 UTC
WORTH KNOWING VERIFY_ONLY APISECURITY
WHAT CHANGEDCloudflare Audit Logs v2 now records view actions corresponding to GET requests for supported endpoints, effective 13 October 2026. The dashboard excludes these view actions by default with an "Action type is not view" filter, but they are always available through the API and Logpush without filtering.
WHY IT MATTERSGET requests can generate high log volumes, potentially increasing storage costs and complicating log analysis if you consume audit logs via API or Logpush. If you process audit logs programmatically without filtering, your ingestion pipeline will now receive significantly more events.
WHAT TO DOReview your Audit Logs v2 API and Logpush configurations. If you consume logs programmatically, add filters to exclude view actions unless you specifically need GET request visibility for security investigations. Check whether increased log volume affects your storage budget or downstream processing capacity.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Audit Logs - Audit Logs v2 now captures view actions
+https://developers.cloudflare.com/changelog/post/2026-10-13-audit-logs-v2-view-actions/
+Tue, 13 Oct 2026 00:00:00 GMT
+
+Audit Logs v2 now records view actions for supported endpoints, providing visibility into read activity across Cloudflare products. These actions correspond to GET requests and provide additional context for security investigations and forensic analysis.
+The Audit Logs v2 dashboard excludes view actions by default to reduce noise. Remove the default Action type is not view filter to include them, or set Action type to view to show only view actions.
+View actions are always available through the Audit Logs v2 API and Logpush, regardless of the dashboard filter.
+CautionGET requests can generate a high volume of audit logs. When using the API or Logpush, apply appropriate filters to limit the volume of delivered logs.
+For more information, refer to the Audit Logs v2 documentation.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.85, needed 0.5
triage reasoningAudit Logs v2 now captures and exposes read activity; teams must understand new logging behavior, dashboard defaults, and volume implications.
signalsnew feature: view actions now captured in Audit Logs v2 · API behavior change: GET requests now logged · dashboard default filter change: view actions excluded by default · security/compliance impact: audit trail expansion · operational warning: high volume potential for GET request logging
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)