Tuning and the count window

Tuning is where you see the count window, the Advisor, virtual-patch cards, and the controls that change a rule. The timeline explains the wait. It does not flip a rule.

One rollup

Analytics and the Advisor read the same WAF traffic rollup. Ranges on Analytics are 24 hours, 7 days, and 30 days. The default is 24 hours. A missing CloudWatch series is “not confirmed,” not zero, on the timeline, the report, and the Advisor.

Sampled breakdowns (paths, countries, and similar) are samples. The product does not turn those samples into exact totals. A fuller log pipeline for exact geography and longer retention is not part of this version.

The timeline

The track runs through the first week. The decision itself stays 24 hours.

Marks on the timeline
MarkWhat it means
StartRules enter count.
12hA CloudWatch series shorter than this, on a closed clock, stays Hold.
24hThe Advisor can say Promote only after this watch window closes, and only when the evidence is complete.
7dA full week in count does not flip a rule. You still click Promote, and only for a rule whose evidence is complete.

The first-day line says managed rules stay in count and that a missing series is not a reason to block. The first-week line says Promote still uses the latest 24-hour rollup, the same numbers as Analytics and the Advisor.

For a Hold or Needs allowlist row, the timeline and the card share one “what would change this” sentence. Promote rows do not get that line.

What you can change here

You can set a managed group to count or block, add a group in count from a virtual-patch card, save or remove an allowlist, and undo a promote. Custom allow, block, and rate rules sit in the same editor, beside the managed groups.

The Launch checklist sits beside Tuning. You pick WordPress, WooCommerce, or another kind of site and record whether login, the editor, media, and a form still work — plus cart, checkout, and the payment return for a store. The add-site form does not ask for that platform. Request tuning review sends the Advisor verdict to support. It does not promote a rule, and it is not a staffed watch.

WordPress and WooCommerce templates sit on the site after the shield is up. The preview lists the groups that would be turned on in count. Apply template (count only) adds those groups in count. It does not promote, and it does not change a group that is already blocking. If the Launch checklist already says WordPress or WooCommerce, the preview starts there. A template is a starting point, not automatic hardening. Promote stays on Tuning. A client viewer cannot apply a template.

Investigate this request is on Events, and on a Tuning sample, when that sample has a rule, a time, and a path. It sends that one request to support. A person reviews it. Nothing is promoted, and no allowlist is saved. When the review is recorded, change history shows a possible false positive with an allowlist suggestion, a confirmed block, or no action. There is no promised reply time. A client viewer can read that history and cannot start or resolve the investigation.

A blocked visitor can send the reference on the block page. The site lists that report with the rule and the Advisor’s last read. A narrow exception, count, or Undo is still a click on this page. A report does not change the rule. See When a visitor is blocked.

The rule capacity shown on Tuning, on the rate cards, and on the under-attack card is 1,500. A save that would not fit stops before anything changes and says what to turn off. The Advisor holds a Promote that would not fit. Hold and Needs allowlist stay as they are. The Advisor does not turn a protection off to make room, and it does not Promote.

Related guides

More in this section