Log Entry
The logentry template represents an individual entry within a log.
Example config:
apiVersion: "config.istio.io/v1alpha2"
kind: logentry
metadata:
name: accesslog
namespace: istio-system
spec:
severity: '"Default"'
timestamp: request.time
variables:
sourceIp: source.ip | ip("0.0.0.0")
destinationIp: destination.ip | ip("0.0.0.0")
sourceUser: source.user | ""
method: request.method | ""
url: request.path | ""
protocol: request.scheme | "http"
responseCode: response.code | 0
responseSize: response.size | 0
requestSize: request.size | 0
latency: response.duration | "0ms"
monitored_resource_type: '"UNSPECIFIED"'
Template
The logentry template represents an individual entry within a log.
When writing the configuration, the value for the fields associated with this template can either be a literal or an expression. Please note that if the datatype of a field is not istio.policy.v1beta1.Value, then the expression’s inferred type must match the datatype of the field.
istio.policy.v1beta1.TimeStamp
An instance field of type TimeStamp denotes that the expression for the field must evalaute to ValueType.TIMESTAMP
Objects of type TimeStamp are also passed to the adapters during request-time for the instance fields of type TimeStamp
istio.policy.v1beta1.Value
An instance field of type Value denotes that the expression for the field is of dynamic type and can evalaute to any
ValueType enum values. For example, when
authoring an instance configuration for a template that has a field data of type istio.policy.v1beta1.Value,
both of the following expressions are valid data: source.ip | ip("0.0.0.0"), data: request.id | "";
the resulting type is either ValueType.IP_ADDRESS or ValueType.STRING for the two cases respectively.
Objects of type Value are also passed to the adapters during request-time. There is a 1:1 mapping between
oneof fields in Value and enum values inside ValueType. Depending on the expression’s evaluated ValueType,
the equivalent oneof field in Value is populated by Mixer and passed to the adapters.