The recommended behaviors are optional behaviors that are either automatically part of your configuration in the default rule, or you can add them to the default rule or custom rules.
This section does not include the insertable-only behaviors that do not include modifiable parameters such as download notification or download complete marker behaviors.
For more information, see:
With this behavior, you can extract unique and static identifiers (UID) of vehicles from live traffic. Extracting UIDs enables logging traffic data for individual vehicle reports, bandwidth and cars reports, and OTA Updates API reporting.
You can configure the UID configuration behavior in the default rule or add any number of UID configuration behaviors in separate custom rules to better control UID extraction from live traffic.
With standard UID configurations, you can extract UIDs from header names and query parameters of your requests. With advanced UID configurations that include user-defined variables you can:
Populate the variable with values extracted from incoming client requests. For example, specific request headers, cookies, URL paths/extensions, string parameters, parts of client certificates, and others.
Manipulate (transform) the variable using a number of different operations. For example, extracting substrings, upper/lower case, search/replace, encode/decode, and others.
For more information on variables, see the "Working with Variables" section of the Property Manager Online Help in Akamai Control Center.
UID configuration parameters
The location that UIDs are extracted from.
The name of a request header that UIDs are extracted from.
The value extracted from the header name ranges from 0 to 20 characters.
Query Parameter Name
The name of a request query parameter that UIDs are extracted from.
The value extracted from the query parameter name ranges from 0 to 20 characters.
The name of the variable configured to extract UIDs from live traffic.
The value extracted from the variable ranges from 0 to 20 characters.
The following table lists the parameters you can specify in the aggregated reporting behavior. With this behavior, you can configure a custom report that aggregates traffic data on up to four user-defined data types. You can only have two aggregated reporting behaviors in an OTA Updates property.
Aggregated reporting parameters
Enables generating aggregated reports.
The unique name of a data source within the property. By default, the name used by an instance of the aggregated report to log data.
Important: If you reconfigure any of the attributes in the aggregated reporting behavior or the variables used as data sources for the attributes, you must change the report name. This change allows a new instance of the aggregated report to log the reconfigured data.
The number of attributes that group the aggregated report. You can add up to four attributes.
The attributes for the aggregated report. These fields use user-defined variables.
The values extracted for all attributes range from 0 to 20 characters.
The following table lists the parameters you can specify in the request type marker behavior. With this behavior, you can distinguish two types of requests coming to the OTA domains. Based on the defined marker, requests are logged in aggregated and individual vehicle reports or in an individual vehicle report only.
Request type marker parameters
Indicates the type of request coming to the OTA domains. Two markers are
Updated 9 months ago