Skip to content

Commit 8ac516d

Browse files
[Analytics] Move and update Custom Dashboards documentation (#30207)
* [Analytics] Move and update Custom Dashboards documentation - Move page from /log-explorer/custom-dashboards/ to /analytics/custom-dashboards/ - Add redirect from old URL to new URL - Update availability: 25 dashboards for all customers, 100 for Log Explorer - Add 100+ GraphQL datasets, dashboard filters, Log Explorer data sections - Rewrite content with use-case focused examples instead of procedural steps - Add new chart types: Bar, Donut, Map - Update DashButton URL to analytics/dashboards * Apply suggestions from code review Co-authored-by: Patricia Santa Ana <103445940+patriciasantaana@users.noreply.github.com> * update dashbutton paths --------- Co-authored-by: Patricia Santa Ana <103445940+patriciasantaana@users.noreply.github.com> Co-authored-by: Patricia Loraine Santa Ana <psantaana@cloudflare.com>
1 parent 752ab3f commit 8ac516d

4 files changed

Lines changed: 156 additions & 109 deletions

File tree

public/__redirects

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,9 @@
33
# STATIC REDIRECTS
44
# ============================================================================
55

6+
# Custom Dashboards (moved from log-explorer to analytics)
7+
/log-explorer/custom-dashboards/ /analytics/custom-dashboards/ 301
8+
69
# Solutions (moved from use-cases/application-security/bots/)
710
/use-cases/application-security/bots/stop-malicious-bots/ /use-cases/solutions/stop-malicious-bots/ 301
811

src/content/dash-routes/core.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
},
1111
{
1212
"name": "Custom dashboards",
13-
"deeplink": "/?to=/:account/log-explorer/dashboards",
13+
"deeplink": "/?to=/:account/analytics/dashboards",
1414
"parent": ["Analytics & logs", "Log Explorer"]
1515
},
1616
{
@@ -470,7 +470,7 @@
470470
},
471471
{
472472
"name": "Custom dashboards",
473-
"deeplink": "/?to=/:account/:zone/log-explorer/dashboards",
473+
"deeplink": "/?to=/:account/:zone/analytics/dashboards",
474474
"parent": ["Log Explorer"]
475475
},
476476
{
Lines changed: 151 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,151 @@
1+
---
2+
pcx_content_type: reference
3+
title: Custom dashboards
4+
sidebar:
5+
order: 4
6+
description: Create custom dashboards to monitor log data.
7+
products:
8+
- log-explorer
9+
---
10+
11+
import { DashButton } from "~/components";
12+
13+
Custom dashboards allow you to build personalized views that highlight the metrics most critical to your infrastructure and security posture. Move beyond standard product dashboards and consolidate data from multiple Cloudflare products into a single, unified view.
14+
15+
<DashButton url="/?to=/:account/analytics/dashboards" />
16+
17+
## What you can do
18+
19+
Monitor security threats by tracking WAF blocks, bot scores, and threat patterns across your zones. Combine HTTP traffic data with security events to correlate attack patterns with traffic spikes.
20+
21+
Analyze application performance by visualizing origin response times, cache hit ratios, and error rates. Identify slow endpoints and understand how latency varies by region or device type.
22+
23+
Track business metrics by monitoring API usage, bandwidth consumption, and traffic patterns. Build executive dashboards that surface the KPIs that matter to your organization.
24+
25+
Investigate incidents so that when something goes wrong, you can create focused dashboards that combine the specific signals relevant to your investigation. Log Explorer customers can turn log queries directly into dashboard charts for ongoing monitoring.
26+
27+
## Availability
28+
29+
Custom Dashboards are available to all Cloudflare customers.
30+
31+
| Customer type | Dashboard limit |
32+
|---------------|-----------------|
33+
| All Cloudflare customers | Up to 25 dashboards |
34+
| Log Explorer customers | Up to 100 dashboards |
35+
36+
## Get started
37+
38+
### Start from a template
39+
40+
Templates are the fastest way to get value from Custom Dashboards. Each template is designed around a specific use case and includes pre-configured charts that surface the most relevant metrics.
41+
42+
| Template | Use case |
43+
|----------|----------|
44+
| **Bot monitoring** | Understand what automated traffic is hitting your site — distinguish good bots (search engines, monitoring) from bad actors |
45+
| **API Security** | Monitor your API endpoints for anomalies, track data transfer volumes, and identify unexpected access patterns |
46+
| **Account takeover** | Watch for credential stuffing attacks by tracking failed login attempts, leaked credential usage, and suspicious authentication patterns |
47+
| **API Performance** | Identify slow API endpoints, track error rates by endpoint, and monitor latency percentiles to catch regressions before users complain |
48+
| **Performance monitoring** | Find bottlenecks in your origin infrastructure — which hosts are slow, which paths have high TTFB, and how performance trends over time |
49+
50+
After selecting a template, you can customize it by adding, removing, or modifying charts to fit your specific needs.
51+
52+
### Build from scratch
53+
54+
For specialized monitoring needs, create a blank dashboard and add charts that query exactly the data you need.
55+
56+
Custom Dashboards support over 100 datasets available via the Cloudflare GraphQL API, including HTTP traffic, security events, Workers analytics, R2 Storage metrics, Load Balancing health, Zero Trust logs, DNS queries, and more.
57+
58+
## Create charts
59+
60+
### Natural language prompts
61+
62+
Describe what you want to see in plain English, and AI will construct the appropriate visualization:
63+
64+
- "Show me error rates by country for the last 24 hours."
65+
- "Compare cached vs uncached requests over time."
66+
- "What are my top 10 paths by request volume?"
67+
- "Display WAF blocks grouped by rule ID."
68+
69+
This is the fastest way to explore your data when you have a question but are not sure which dataset or metric to use.
70+
71+
### Manual configuration
72+
73+
For precise control, configure each element of your chart:
74+
75+
- **Dataset** — The data source to query (HTTP requests, security events, Workers metrics, etc.)
76+
- **Metrics** — What to measure (requests, bytes, duration) and how to aggregate it (sum, average, percentiles)
77+
- **Dimensions** — How to break down the data (by country, status code, hostname, etc.)
78+
- **Filters** — Conditions to narrow the data (specific paths, IP ranges, user agents, etc.)
79+
80+
### Chart types
81+
82+
Choose the visualization that best fits your data:
83+
84+
| Chart type | Best for |
85+
|------------|----------|
86+
| **Timeseries** | Trends and patterns over time — traffic spikes, latency changes, error rate fluctuations |
87+
| **Bar** | Comparing values across categories — requests by country, errors by status code |
88+
| **Donut** | Understanding proportions — cache hit ratio, traffic distribution by content type |
89+
| **Map** | Geographic patterns — where your traffic originates, regional performance differences |
90+
| **Stat** | Single important numbers — total requests today, current error rate, p99 latency |
91+
| **Percentage** | Ratios and rates — cache hit percentage, bot traffic proportion |
92+
| **Top N** | Rankings — busiest endpoints, most blocked IPs, top user agents |
93+
94+
#### Example: Build a security overview chart
95+
96+
To track blocked requests by WAF rule:
97+
98+
1. Select the **Security Events** dataset.
99+
2. Choose **Events** as the metric with **Total** aggregation.
100+
3. Add **Rule ID** as a dimension to group by rule.
101+
4. Filter to **Action equals Block** to focus on blocked traffic.
102+
5. Select **Bar** chart to compare rule effectiveness.
103+
104+
The result shows which WAF rules are triggering most frequently, helping you understand your threat landscape and tune your security configuration.
105+
106+
## Dashboard filters
107+
108+
Dashboard filters apply to all charts at once, making it easy to focus your entire dashboard on a specific segment of traffic.
109+
110+
Common uses:
111+
112+
- **Time range** — Zoom into a specific incident window across all charts
113+
- **Hostname** — Focus on a single domain when you manage multiple properties
114+
- **Country** — Analyze traffic patterns for a specific region
115+
- **Status code** — Investigate error spikes by filtering to `5xx` responses
116+
117+
When you add a filter, every chart on the dashboard updates to reflect the narrowed scope.
118+
119+
## Log Explorer data
120+
121+
:::note
122+
This feature is available to Log Explorer customers only.
123+
:::
124+
125+
Log Explorer customers can create charts and dashboards using their raw, unsampled log data. This is useful when precision matters — for example, when monitoring for specific error conditions, tracking exact request counts for compliance reporting, or analyzing low-volume but high-impact events that might be missed in sampled data.
126+
127+
Standard analytics datasets use sampled data, which provides fast, accurate trends for high-volume metrics. But for use cases like:
128+
129+
- **Exact counts** — "How many requests from this specific IP hit our API today?"
130+
- **Rare events** — Monitoring for specific error codes or attack signatures that occur infrequently
131+
- **Compliance and auditing** — When you need precise numbers, not estimates
132+
- **Low-traffic endpoints** — Analyzing paths that do not generate enough volume for reliable sampling
133+
134+
Log Explorer data gives you charts built from every logged event, not a statistical sample.
135+
136+
When creating a chart, Log Explorer customers can select from Log Explorer datasets alongside the standard GraphQL analytics datasets.
137+
138+
## Manage dashboards
139+
140+
Dashboards are organized in a list view where you can see all dashboards in your account. From any dashboard, you can add, remove, or rearrange charts, and changes are saved automatically when you exit edit mode.
141+
142+
Each chart has a menu with options to edit its configuration, duplicate it, or drill down into related data in Security Analytics or Log Search.
143+
144+
## Further analysis
145+
146+
Custom Dashboards are designed to work alongside other Cloudflare analytics tools:
147+
148+
- **Security Analytics** — When a chart reveals suspicious traffic, drill down to investigate individual requests and see full request details
149+
- **Log Search** — Move from aggregated metrics to raw logs when you need to understand exactly what happened during an incident
150+
151+
This workflow supports the typical investigation pattern: start with high-level dashboards to identify anomalies, then drill into detailed logs to understand root cause.

src/content/docs/log-explorer/custom-dashboards.mdx

Lines changed: 0 additions & 107 deletions
This file was deleted.

0 commit comments

Comments
 (0)