Log Explorer queries moved to Observability Logs page
Log Explorer datasets are now queried from the unified Logs page under Observability, which combines Log Explorer and Workers Observability datasets with a shared filter builder, SQL editor, and visualizations. The Log Explorer menu has been removed from dashboard navigation, though all enabled datasets and saved queries remain functional.
Log Explorer datasets are now queried from the Logs page under Observability in the Cloudflare dashboard. The Logs page brings Log Explorer and Workers Observability datasets together with a shared filter builder, SQL editor, and visualizations.
As part of this change, the Log Explorer menu is no longer shown in the dashboard navigation.
- Your enabled datasets, saved queries, and SQL queries continue to work on the Logs page.
- To manage datasets, open the dataset selector on the Logs page and select Configure next to the Log Explorer datasets.
- The previous Log Search page remains available at its direct URL.
For more information, refer to Log Search and the Logs overview.
Source: original entry ↗
More from Cloudflare
Follow Cloudflare to get its new changes in your feed and email digest.
Cloudflare API MCP server now serves Cloudflare skills
The Cloudflare API MCP server now integrates with the Skills over MCP extension, allowing MCP clients to discover and access Cloudflare skills. Users can add the MCP server endpoint to compatible MCP clients to access these skills.
WAF failed detections field now available in Rules
A new cf.appsec.request.failed_detections field lets you control how rules handle requests when security detections fail. This array of detection IDs covers content scanning, WAF attack scoring, attack signatures, leaked credentials, and AI-based PII/prompt injection/custom topic detection failures, and works across custom rules, rate limiting rules, and request header transform rules.
Markdown for Agents: More efficient in-process streaming conversion
Markdown for Agents now uses an in-process streaming engine at the edge to convert HTML, reducing overhead and memory use. The conversion limit increased from 2 MiB to 6 MiB, and token count headers are no longer generated.