Attributes are a central concept used throughout Istio. You can find a description of what attributes are and what they are used for here.
A given Istio deployment has a fixed vocabulary of attributes that it understands. The specific vocabulary is determined by the set of attribute producers being used in the deployment. The primary attribute producer in Istio is Envoy, although Mixer and services can also introduce attributes.
The table below shows the set of canonical attributes and their respective types. Most Istio deployments will have agents (Envoy or Mixer adapters) that produce these attributes.
|Client IP address.
|The fully qualified name of the service that the client belongs to.
|The short name part of the source service.
|The namespace part of the source service.
|The domain suffix part of the source service, excluding the name and the namespace.
|Platform-specific unique identifier for the client instance of the source service.
|A map of key-value pairs attached to the client instance.
|version => v1
|The identity of the immediate sender of the request, authenticated by mTLS.
|Server IP address.
|The recipient port on the server IP address.
|The fully qualified name of the service that the server belongs to.
|The short name part of the destination service.
|The namespace part of the destination service.
|The domain suffix part of the destination service, excluding the name and the namespace.
|Platform-specific unique identifier for the server instance of the destination service.
|A map of key-value pairs attached to the server instance.
|version => v2
|The user running the destination application.
|HTTP request headers. For gRPC, its metadata will be here.
|An ID for the request with statistically low probability of collision.
|The HTTP URL path including query string
|HTTP/1.x host header or HTTP/2 authority header.
|The HTTP method.
|The request reason used by auditing systems.
|The HTTP referer header.
|URI Scheme of the request
|Size of the request in bytes. For HTTP requests this is equivalent to the Content-Length header.
|Total size of HTTP request in bytes, including request headers, body and trailers.
|The timestamp when the destination receives the request. This should be equivalent to Firebase “now”.
|The HTTP User-Agent header.
|HTTP response headers.
|Size of the response body in bytes
|Total size of HTTP response in bytes, including response headers and body.
|The timestamp when the destination produced the response.
|The amount of time the response took to generate.
|The response's HTTP status code.
|An ID for a TCP connection with statistically low probability of collision.
|Status of a TCP connection, its value is one of “open”, “continue” and “close”.
|Number of bytes received by a destination service on a connection since the last Report() for a connection.
|Total number of bytes received by a destination service during the lifetime of a connection.
|Number of bytes sent by a destination service on a connection since the last Report() for a connection.
|Total number of bytes sent by a destination service during the lifetime of a connection.
|The total amount of time a connection has been open.
|Indicates whether a request is received over a mTLS enabled downstream connection.
|Protocol of the request or connection being proxied.
|The timestamp of Mixer operation.
|The public service name. This is different than the in-mesh service identity and reflects the name of the service exposed to the client.
|The API version.
|Unique string used to identify the operation. The id is unique among all operations described in a specific <service, version>.
|The protocol type of the API call. Mainly for monitoring/analytics. Note that this is the frontend protocol exposed to the client, not the protocol implemented by the backend service.
|“http”, “https”, or “grpc”
|The authenticated principal of the request. This is a string of the issuer (
iss) and subject (
sub) claims within a JWT concatenated with “/” with a percent-encoded subject value. This attribute may come from the peer or the origin in the Istio authentication policy, depending on the binding rule defined in the Istio authentication policy.
|The intended audience(s) for this authentication information. This should reflect the audience (
aud) claim within a JWT.
|The authorized presenter of the credential. This value should reflect the optional Authorized Presenter (
azp) claim within a JWT or the OAuth2 client id.
|all raw string claims from the
|The API key used for the request.
|The error code for Mixer Check call.
|The error message for Mixer Check call.
|Could not find the resource
|Indicates whether Mixer check call hits local cache.
|Indicates whether Mixer quota call hits local cache.