--- title: Log Entry overview: A template that represents a single runtime log entry. location: https://istio.io/docs/reference/config/template/logentry.html layout: protoc-gen-docs number_of_entries: 1 ---

The logentry template represents an individual entry within a log.

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.mixer.v1.template.Value, then the expression’s inferred type must match the datatype of the field.

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"'
Field Type Description
variables map<string, istio.mixer.v1.template.Value>

Variables that are delivered for each log entry.

timestamp istio.mixer.v1.template.TimeStamp

Timestamp is the time value for the log entry

severity string

Severity indicates the importance of the log entry.

monitoredResourceType string

Optional. An expression to compute the type of the monitored resource this log entry is being recorded on. If the logging backend supports monitored resources, these fields are used to populate that resource. Otherwise these fields will be ignored by the adapter.

monitoredResourceDimensions map<string, istio.mixer.v1.template.Value>

Optional. A set of expressions that will form the dimensions of the monitored resource this log entry is being recorded on. If the logging backend supports monitored resources, these fields are used to populate that resource. Otherwise these fields will be ignored by the adapter.