# Get started with Analytics

> Read a zone's traffic and security events, then turn on Real User Monitoring to measure Core Web Vitals from real visits.

## Before you begin

- A zone with proxied names that receive traffic through the edge. See [DNS](https://developers.openwaf.dev/dns/).
- Any role can read analytics. Turning on Real User Monitoring needs the `tech` or `admin` role.

## Steps

1. **Open the traffic counters.** In the zone, go to **Analytics › Traffic**. The top cards show requests, blocked requests, bandwidth out and DNS queries for the chosen **Period** (last 7, 30 or 90 days), with a chart per day.

2. **Look at the security events.** Scroll down to **Security events**: what the firewall blocked, challenged or logged, with filters and a **Live** mode. See [Security events](https://developers.openwaf.dev/analytics/security-events/).

3. **Turn on Real User Monitoring.** Go to **Analytics › Real performance**, choose a **Sample rate** and select **Enable**.

   ```sh
   openwaf-cloud ctl zones set example.com rum.enabled=true --reason "measure web vitals"
   ```

4. **Visit your site.** Open a few pages in a browser and close the tab. Data appears about a minute after a visitor leaves a page or switches tab.

5. **Read the report.** **Analytics › Real performance** shows the Core Web Vitals assessment, one tile per metric and diagnostics. See [Core Web Vitals](https://developers.openwaf.dev/analytics/core-web-vitals/).

   ```sh
   openwaf-cloud ctl rum report example.com --since 24h
   ```


## Next steps

- [Real User Monitoring](https://developers.openwaf.dev/analytics/real-user-monitoring/): sampling, excluded paths, per-name settings and CSP.
- [RUM privacy](https://developers.openwaf.dev/analytics/rum-privacy/): what the script measures and what it never collects.