Advanced analytics
This tool shows where requests to your website or application most often come from: IP addresses, subnets, user agents, and countries. It also shows which method + path combinations occur most often in requests.
Why use Advanced analytics?
You will see five tabs. Each tab contains the top 100 values for a different traffic characteristic.
Use Advanced analytics to find anomalies and potential weak points and to analyze your traffic structure.
Here are two examples of how the tool can help. Click a heading to expand its description.
Protect an endpoint from overload
You open Advanced analytics on the Top requests tab and notice many requests to the /search/advanced page. This page provides advanced search on your website. The feature is useful but resource-intensive, so more requests could overload the backend.
You decide to find out who accesses this page. You open Request logs and add the filter Path = /search/advanced. The logs show that both people and bots request the page actively. The bots appear to be parsing content.
To reduce the load, you add a custom rule for this page: block bots (Bot, Likely bot) and give all other requests a JS challenge. As a result, the extra load disappears, and real users can use search without issues.
Learn more about your users
Your application has several versions, and each sends its own User-Agent.
You open Top user agents and see that the User-Agent of an older version is the most common, while newer versions are less common. This is unexpected: many users are not updating for some reason. You decide to collect more data by filtering traffic first by the older User-Agent and then by the newer one. Top countries shows that users of the older version are mostly in one region.
This gives you a valuable insight that you can use when making product decisions.
Configure filters
You can filter data flexibly to see a specific traffic segment. For example, you can show statistics only for bot requests that did not pass a CAPTCHA.
1. Open Advanced analytics
Go to Application protection → Resources. Next to the required resource, click … and select Advanced analytics.
2. Select the period
Click Last 24 hours to open the Period menu. You can use one of the standard options (the last 5, 15, or 30 minutes; or 1, 3, 6, 12, or 24 hours) or specify a custom range.
3. Add filters
| You can add several filters. They use AND logic: you see only traffic that matches all filters at the same time. |
Click Add filter and select the filter type. There are three types:
-
Actionfilters by the action that protection applied to a request: block, pass, or challenge. -
Src. classfilters by the request source: whether a bot or a person sent it. -
Action reasonfilters by why protection applied an action. For example, it passed a request to your resource (action) because the request came from an IP address on your white list (reason).
Then select an operator:
-
equals—specify one exact value that traffic must match. -
not equals—specify one value that traffic must not match. -
in—specify several values, and traffic must match at least one of them. -
not in—specify several values, and traffic must not match any of them.
Then specify a value. The available values depend on the filter. Click a heading to expand the list.
Action filter values
Block—the request is blocked.
Pass—the request is passed to the origin server.
Captcha challenge—the client receives a CAPTCHA.
Cookie challenge—the client receives a cookie challenge.
JS challenge—the client receives a JS challenge.
Src. class filter values
Human—a person definitely sent the request.
Likely human—a person most likely sent the request, but protection is not completely certain.
Likely bot—a bot most likely sent the request, but protection is not completely certain.
Bot—a bot definitely sent the request.
Action reason filter values
Behavior pass—behavioral analysis identified the user as legitimate.
Captcha invalid—the user did not complete the CAPTCHA correctly.
Captcha pass—the user completed a CAPTCHA successfully recently and confirmed that they are legitimate.
Captcha set cookie redirect—the user has already completed a CAPTCHA successfully. Strictera is now setting a cookie that lets the user access your resource without challenges for some time.
Check force—according to the current security policy, this request requires an additional challenge.
Conn blocked by hosting—the subnet has a poor reputation and often sends bot requests.
Conn blocked by no cookie—the request had to contain a Strictera cookie but did not.
Custom white bot—we allowlisted this type of traffic at your request.
Invalid method—the client used an HTTP request method that is incompatible with the location that received the request.
Invalid uid—protection detected changes to the cookie, so the traffic is suspicious.
Ip blocked—this IP address recently sent suspicious requests and is temporarily blocked. To find out why it was first blocked, open the logs of previous requests from this IP address.
Ip blocked by spec—the user exceeded one of the rate limits set by the protection policy for your resource.
Local bgeo—the request came from a country that you blocked in Geo restrictions.
Local black—the request came from an IP address that you added to the black list.
Local whdr—the request contains an allowed HTTP header with limited trust. Protection passes such requests without checks until their number exceeds the set limit, for example 2,000 requests per minute. The filtering policy configured for your resource checks all requests above the limit.
Local whd—the request contains an allowed HTTP header. Requests with this header are passed to your origin server.
Local white—the request came from an IP address that you added to the white list.
Mobile app—the traffic is classified as traffic from a legitimate mobile application.
None—the request does not match the white list, black list, custom rules, or the individual protection profile. Protection applies its base filtering policy: the standard system response that depends on the request source class (bot, likely bot, likely human, or human).
Protection disabled—protection is disabled. This applies both when protection is disabled for the specific location that received the request and when it is disabled for the whole resource.
user_blocked—the request came from a blocked user. The decision to block the user was made during one of their previous requests.
user_blocked_by_behavior—behavioral analysis detected anomalous activity. The user’s requests are blocked starting with this one.
user_blocked_by_no_correct_cookie—the user sent a request without the required cookie, which indicates that the user is not legitimate. The user’s requests are blocked starting with this one.
user_blocked_by_score—analysis of the user’s actions and characteristics identified the user as not legitimate. The user’s requests are blocked starting with this one.
user_blocked_by_spec—the user exceeded one of the rate limits set by the protection policy for your resource. The user’s requests are blocked starting with this one.
white—the request came from an officially verified bot that performs a useful task on the internet, such as a search engine crawler or uptime monitoring service. Protection continuously checks and updates the list of such bots. Their requests are passed without checks by default.
white_corp—the request came from a subnet that we allowlisted at your request.
Example filter configuration:
Task: find requests from illegitimate bots that protection blocked.
Configuration:
-
Add the first filter:
ActionequalsBlock. -
Click
Add filteragain to add the second filter. -
Add the second filter:
Src. classinBot,Likely bot. -
Click
Apply.
Result: the lists contain only requests from bots blocked by protection. You see the IP addresses, subnets, and user agents that sent the requests, as well as the endpoints and countries involved.