Common
The Common dimension group provides data in a number of dimensions common to all incoming requests.
When you select a dimension, you can see the total number of requests, a graph with the average number of requests per second at given moments within the displayed time period, a table with additional details on the dimension, and a graphical display of request distribution within the selected time period.
- IP address
- The dimension provides request data by IP address. Note: Country, company, and domain are calculated at run time, so while it’s possible these values could be different subsequent to the event’s triggering, occurrences like this are rare.
In addition, you can have the table display either the Connecting IP Address (the IP address that connected to Akamai’s edge servers) or the End User IP Address (which will differ from the connecting IP address if the edge server acted on an IP address taken from the x-forwarded-for header).
- IP subnet
- The dimension provides request data by IP subnet. These are calculated by
truncating the IP address to a /24 netmask for IPv4 and a /64 netmask for IPv6.
In addition, you can have the table display either the Connecting IP Subnet or the End User IP Subnet.
- AS number
- The dimension provides request data by AS (autonomous system) number, which
identifies the originating network.
In addition, you can have the table display either the Connecting AS Number or the End User AS Number. AS numbers are calculated by a reverse look up on the connecting IP addresses or the end users’ IP addresses at the time the requests were received by Akamai’s edge servers.
- Country/Area
- The dimension provides request data by geography.
In addition, you can have the table display either the Connecting Country/Area or the End User Country/Area. Country/area is calculated by a reverse look up on the connecting IP address or the end user IP address at the time the request was received by Akamai’s edge servers.
- Hostname
- The dimension provides request data by hostname.
- Path
- The dimension provides request data by path.
- Query
- The dimension provides request data by query string. Note: In the Statistics View, if a query string is longer than 1000 characters, the system trims it to the first 1000 characters and adds a “[TRUNCATED]” suffix. You can still see the full query value in the Sample Log view.
- URL
- The dimension provides request data by URL.
- User-Agent
- The dimension provides request data by User-Agent header.
- SDK version
- The dimension lets you filter on a version of Bot Manager Premier Mobile
Protection Module that you use to protect native mobile apps.Note: The returned value may be empty if the request came from a web client or the request was stopped by an edge detection, for example with a reason code 3902001. For more information about the code, see Behavioral detection
- Native mobile app version
- For Bot Manager Premier only. The dimension lets you filter on a version
you entered when defining your native mobile apps. It can be, for example, the Earliest
app version with SDK integrated or Earliest app version using Proof-of-Work
feature.Note: The returned value may be empty if you have no User agent version prefix defined for your native mobile application.
- Action
- The dimension provides request data by action type such as alert and deny.
- API ID
- The dimension provides request data by your API IDs.Note: The API ID dimension is only available if API protections are enabled.
- API resource purpose name
- The API resource purpose name dimension for bot management shows request data by individual API resource purpose names you defined when registering an API. This value is the name you gave to any transactional endpoints you defined in order manage their bot traffic using behavior anomaly detections.
- API resource purpose type
- The API resource purpose type dimension for bot management lets you see request data by the types you assigned to API resource purposes. Type is the task a resource serves, like login. You define and name an individual API resource purpose when you register an API. Then you can manage its bot traffic using behavior anomaly detections.
- Origin response
- View request data grouped by the response to the requests forwarded to the protected
endpoints on your origin server:
- Fail - the request was rejected.
- Success - the request was fulfilled.
- Unknown - the request doesn’t meet the defined criteria to be a failure or success.
- API key
- The API
Key dimension provides request data by your API keys.Note: The API key dimension is only available if API protections are enabled.
- Policy
- The dimension provides request data by your firewall policies. Note: Policy name is the current name assigned to the policy ID. Should the name change during the displayed analysis period, the new name used.
- Status code
- The dimension provides request data by status code.