Package org.zalando.riptide.opentracing
Class ExtensionTags
java.lang.Object
org.zalando.riptide.opentracing.ExtensionTags
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final io.opentracing.tag.Tag<String>The tag should contain an alias or name that allows users to identify the logical location (infrastructure account) where the operation took place.static final io.opentracing.tag.Tag<String>The tag should contain the artifact version of the running application generating the spans.static final io.opentracing.tag.Tag<String>Oauth2 client ids have a certain cardinality but are well known or possible to get using different means.static final io.opentracing.tag.Tag<String>The tag should contain the unique identifier of the deployment that resulted in the operation of the running application generating the spans.static final io.opentracing.tag.Tag<String>The flow_id tag should contain the request flow ID, typically found in the ingress requests HTTP header X-Flow-ID.static final io.opentracing.tag.Tag<String>static final io.opentracing.tag.Tag<String>Remote "address", suitable for use in a networking client library.static final io.opentracing.tag.Tag<Boolean>When present on a client span, they represent a span that wraps a retried RPC.static final io.opentracing.tag.Tag<String>The tag should contain some information that allows users to associate the physical location of the system where the operation took place (i.e. the datacenter). -
Method Summary
-
Field Details
-
HTTP_PATH
-
RETRY
When present on a client span, they represent a span that wraps a retried RPC. If missing no interpretation can be made. An explicit value of false would explicitly mean it is a first RPC attempt. -
ACCOUNT
The tag should contain an alias or name that allows users to identify the logical location (infrastructure account) where the operation took place. This can be the AWS account, or any other cloud provider account. E.g.,account=aws:zalando-zmon,account=gcp:zalando-foobar -
ZONE
The tag should contain some information that allows users to associate the physical location of the system where the operation took place (i.e. the datacenter). E.g.,zone=aws:eu-central-1a,zone=gcp:europe-west3-b,zone=dc:gth. -
CLIENT_ID
Oauth2 client ids have a certain cardinality but are well known or possible to get using different means. It could be helpful for server spans to identify the client making the call. E.g.,client_id=cognac -
FLOW_ID
The flow_id tag should contain the request flow ID, typically found in the ingress requests HTTP header X-Flow-ID. X-Flow-ID Guidelines -
ARTIFACT_VERSION
The tag should contain the artifact version of the running application generating the spans. This is, usually, the docker image tag. -
DEPLOYMENT_ID
The tag should contain the unique identifier of the deployment that resulted in the operation of the running application generating the spans. This is, usually, the STUPS stack version or the Kubernetes deployment id. A deployment is the combination of a given artifact_version and the environment, usually its configuration. -
PEER_ADDRESS
Remote "address", suitable for use in a networking client library. This may be a "ip:port", a bare "hostname", a FQDN, or even a JDBC substring like "mysql://prod-db:3306". Be aware that this will be removed as soon asTagscontains it.- See Also:
-