diff --git a/content/docs/1.12/deployment.md b/content/docs/1.12/deployment.md index 4e2554fd..1c397a6c 100644 --- a/content/docs/1.12/deployment.md +++ b/content/docs/1.12/deployment.md @@ -100,7 +100,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--jaeger.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--jaeger.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--jaeger.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--jaeger.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`. ## Collectors diff --git a/content/docs/1.13/deployment.md b/content/docs/1.13/deployment.md index 834598ba..62e3481a 100644 --- a/content/docs/1.13/deployment.md +++ b/content/docs/1.13/deployment.md @@ -105,7 +105,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--jaeger.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--jaeger.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--jaeger.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--jaeger.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collectors diff --git a/content/docs/1.14/deployment.md b/content/docs/1.14/deployment.md index d27d817a..f8350614 100644 --- a/content/docs/1.14/deployment.md +++ b/content/docs/1.14/deployment.md @@ -105,7 +105,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--jaeger.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--jaeger.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--jaeger.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--jaeger.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`. ## Collectors diff --git a/content/docs/1.15/deployment.md b/content/docs/1.15/deployment.md index f11f332a..35c19227 100644 --- a/content/docs/1.15/deployment.md +++ b/content/docs/1.15/deployment.md @@ -107,7 +107,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--jaeger.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--jaeger.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--jaeger.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--jaeger.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`. ## Collectors diff --git a/content/docs/1.16/deployment.md b/content/docs/1.16/deployment.md index 160e85db..03d007d9 100644 --- a/content/docs/1.16/deployment.md +++ b/content/docs/1.16/deployment.md @@ -107,7 +107,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`. ## Collectors diff --git a/content/docs/1.16/operator.md b/content/docs/1.16/operator.md index 166f3d63..5d0f35fc 100644 --- a/content/docs/1.16/operator.md +++ b/content/docs/1.16/operator.md @@ -976,7 +976,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.17/deployment.md b/content/docs/1.17/deployment.md index ea26ddc4..ffb1fd5a 100644 --- a/content/docs/1.17/deployment.md +++ b/content/docs/1.17/deployment.md @@ -107,7 +107,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. This feature is not supported for the tchannel reporter, enabled using the flags `--collector.host-port` or `--reporter.tchannel.host-port`. ## Collectors diff --git a/content/docs/1.17/operator.md b/content/docs/1.17/operator.md index a86dff5e..92216512 100644 --- a/content/docs/1.17/operator.md +++ b/content/docs/1.17/operator.md @@ -701,16 +701,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1142,7 +1142,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.18/deployment.md b/content/docs/1.18/deployment.md index 313d6a15..b608fd08 100644 --- a/content/docs/1.18/deployment.md +++ b/content/docs/1.18/deployment.md @@ -108,7 +108,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collectors diff --git a/content/docs/1.18/operator.md b/content/docs/1.18/operator.md index 884dbde2..9b71dfad 100644 --- a/content/docs/1.18/operator.md +++ b/content/docs/1.18/operator.md @@ -717,16 +717,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1158,7 +1158,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.19/deployment.md b/content/docs/1.19/deployment.md index a2ec80ca..23211461 100644 --- a/content/docs/1.19/deployment.md +++ b/content/docs/1.19/deployment.md @@ -108,7 +108,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collectors diff --git a/content/docs/1.19/operator.md b/content/docs/1.19/operator.md index b1bd8654..53976918 100644 --- a/content/docs/1.19/operator.md +++ b/content/docs/1.19/operator.md @@ -783,16 +783,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1226,7 +1226,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.20/deployment.md b/content/docs/1.20/deployment.md index a2ec80ca..23211461 100644 --- a/content/docs/1.20/deployment.md +++ b/content/docs/1.20/deployment.md @@ -108,7 +108,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collectors diff --git a/content/docs/1.20/operator.md b/content/docs/1.20/operator.md index b1bd8654..53976918 100644 --- a/content/docs/1.20/operator.md +++ b/content/docs/1.20/operator.md @@ -783,16 +783,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1226,7 +1226,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.21/deployment.md b/content/docs/1.21/deployment.md index a2ec80ca..23211461 100644 --- a/content/docs/1.21/deployment.md +++ b/content/docs/1.21/deployment.md @@ -108,7 +108,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collectors diff --git a/content/docs/1.21/operator.md b/content/docs/1.21/operator.md index c1e403c3..8d1a4a27 100644 --- a/content/docs/1.21/operator.md +++ b/content/docs/1.21/operator.md @@ -783,16 +783,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1226,7 +1226,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.22/deployment.md b/content/docs/1.22/deployment.md index 5d7b6f2b..fe3d194b 100644 --- a/content/docs/1.22/deployment.md +++ b/content/docs/1.22/deployment.md @@ -106,7 +106,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collectors diff --git a/content/docs/1.22/operator.md b/content/docs/1.22/operator.md index b1bd8654..53976918 100644 --- a/content/docs/1.22/operator.md +++ b/content/docs/1.22/operator.md @@ -783,16 +783,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1226,7 +1226,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.23/deployment.md b/content/docs/1.23/deployment.md index 229e4671..c3c0f9a4 100644 --- a/content/docs/1.23/deployment.md +++ b/content/docs/1.23/deployment.md @@ -106,7 +106,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collectors diff --git a/content/docs/1.23/operator.md b/content/docs/1.23/operator.md index b1bd8654..53976918 100644 --- a/content/docs/1.23/operator.md +++ b/content/docs/1.23/operator.md @@ -783,16 +783,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1226,7 +1226,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.24/deployment.md b/content/docs/1.24/deployment.md index 79610d4d..e9be2c60 100644 --- a/content/docs/1.24/deployment.md +++ b/content/docs/1.24/deployment.md @@ -106,7 +106,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collectors diff --git a/content/docs/1.24/operator.md b/content/docs/1.24/operator.md index b1bd8654..53976918 100644 --- a/content/docs/1.24/operator.md +++ b/content/docs/1.24/operator.md @@ -783,16 +783,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1226,7 +1226,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.25/deployment.md b/content/docs/1.25/deployment.md index 2714f14d..ceb76862 100644 --- a/content/docs/1.25/deployment.md +++ b/content/docs/1.25/deployment.md @@ -106,7 +106,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collectors diff --git a/content/docs/1.25/operator.md b/content/docs/1.25/operator.md index be18a235..a9bd9afd 100644 --- a/content/docs/1.25/operator.md +++ b/content/docs/1.25/operator.md @@ -825,16 +825,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1268,7 +1268,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.26/deployment.md b/content/docs/1.26/deployment.md index 2714f14d..ceb76862 100644 --- a/content/docs/1.26/deployment.md +++ b/content/docs/1.26/deployment.md @@ -106,7 +106,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collectors diff --git a/content/docs/1.26/operator.md b/content/docs/1.26/operator.md index be18a235..a9bd9afd 100644 --- a/content/docs/1.26/operator.md +++ b/content/docs/1.26/operator.md @@ -825,16 +825,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1268,7 +1268,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.27/deployment.md b/content/docs/1.27/deployment.md index 2714f14d..ceb76862 100644 --- a/content/docs/1.27/deployment.md +++ b/content/docs/1.27/deployment.md @@ -106,7 +106,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collectors diff --git a/content/docs/1.27/operator.md b/content/docs/1.27/operator.md index be18a235..a9bd9afd 100644 --- a/content/docs/1.27/operator.md +++ b/content/docs/1.27/operator.md @@ -825,16 +825,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1268,7 +1268,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.28/deployment.md b/content/docs/1.28/deployment.md index e42416bd..77b4176a 100644 --- a/content/docs/1.28/deployment.md +++ b/content/docs/1.28/deployment.md @@ -106,7 +106,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collectors diff --git a/content/docs/1.28/operator.md b/content/docs/1.28/operator.md index 274c898c..5eb41bd2 100644 --- a/content/docs/1.28/operator.md +++ b/content/docs/1.28/operator.md @@ -825,16 +825,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1268,7 +1268,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.29/deployment.md b/content/docs/1.29/deployment.md index dcf9e0e8..672b0320 100644 --- a/content/docs/1.29/deployment.md +++ b/content/docs/1.29/deployment.md @@ -135,7 +135,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.29/operator.md b/content/docs/1.29/operator.md index c3e780eb..2938324d 100644 --- a/content/docs/1.29/operator.md +++ b/content/docs/1.29/operator.md @@ -805,16 +805,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1248,7 +1248,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.30/deployment.md b/content/docs/1.30/deployment.md index d461b227..1bf9f805 100644 --- a/content/docs/1.30/deployment.md +++ b/content/docs/1.30/deployment.md @@ -135,7 +135,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.30/operator.md b/content/docs/1.30/operator.md index c3e780eb..2938324d 100644 --- a/content/docs/1.30/operator.md +++ b/content/docs/1.30/operator.md @@ -805,16 +805,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1248,7 +1248,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.31/deployment.md b/content/docs/1.31/deployment.md index d461b227..1bf9f805 100644 --- a/content/docs/1.31/deployment.md +++ b/content/docs/1.31/deployment.md @@ -135,7 +135,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.31/operator.md b/content/docs/1.31/operator.md index f188016c..5c85e144 100644 --- a/content/docs/1.31/operator.md +++ b/content/docs/1.31/operator.md @@ -813,16 +813,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1256,7 +1256,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.32/deployment.md b/content/docs/1.32/deployment.md index d461b227..1bf9f805 100644 --- a/content/docs/1.32/deployment.md +++ b/content/docs/1.32/deployment.md @@ -135,7 +135,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.32/operator.md b/content/docs/1.32/operator.md index f188016c..5c85e144 100644 --- a/content/docs/1.32/operator.md +++ b/content/docs/1.32/operator.md @@ -813,16 +813,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1256,7 +1256,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.33/deployment.md b/content/docs/1.33/deployment.md index 61a5b01f..d826500e 100644 --- a/content/docs/1.33/deployment.md +++ b/content/docs/1.33/deployment.md @@ -138,7 +138,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.33/operator.md b/content/docs/1.33/operator.md index ce4fb823..90e42dcb 100644 --- a/content/docs/1.33/operator.md +++ b/content/docs/1.33/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1301,7 +1301,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.34/deployment.md b/content/docs/1.34/deployment.md index 61a5b01f..d826500e 100644 --- a/content/docs/1.34/deployment.md +++ b/content/docs/1.34/deployment.md @@ -138,7 +138,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.34/operator.md b/content/docs/1.34/operator.md index ce4fb823..90e42dcb 100644 --- a/content/docs/1.34/operator.md +++ b/content/docs/1.34/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1301,7 +1301,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.35/deployment.md b/content/docs/1.35/deployment.md index 61a5b01f..d826500e 100644 --- a/content/docs/1.35/deployment.md +++ b/content/docs/1.35/deployment.md @@ -138,7 +138,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.35/operator.md b/content/docs/1.35/operator.md index ce4fb823..90e42dcb 100644 --- a/content/docs/1.35/operator.md +++ b/content/docs/1.35/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1301,7 +1301,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.36/deployment.md b/content/docs/1.36/deployment.md index 971b0265..a90222bd 100644 --- a/content/docs/1.36/deployment.md +++ b/content/docs/1.36/deployment.md @@ -138,7 +138,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.36/operator.md b/content/docs/1.36/operator.md index ce4fb823..90e42dcb 100644 --- a/content/docs/1.36/operator.md +++ b/content/docs/1.36/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1301,7 +1301,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.37/deployment.md b/content/docs/1.37/deployment.md index 753563f5..9f2916da 100644 --- a/content/docs/1.37/deployment.md +++ b/content/docs/1.37/deployment.md @@ -147,7 +147,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.37/operator.md b/content/docs/1.37/operator.md index ce4fb823..90e42dcb 100644 --- a/content/docs/1.37/operator.md +++ b/content/docs/1.37/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1301,7 +1301,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.38/deployment.md b/content/docs/1.38/deployment.md index d5f5fce2..cd37adc0 100644 --- a/content/docs/1.38/deployment.md +++ b/content/docs/1.38/deployment.md @@ -147,7 +147,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.38/operator.md b/content/docs/1.38/operator.md index ce4fb823..90e42dcb 100644 --- a/content/docs/1.38/operator.md +++ b/content/docs/1.38/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1301,7 +1301,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.39/deployment.md b/content/docs/1.39/deployment.md index 7a01985e..5736af58 100644 --- a/content/docs/1.39/deployment.md +++ b/content/docs/1.39/deployment.md @@ -147,7 +147,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.39/operator.md b/content/docs/1.39/operator.md index ce4fb823..90e42dcb 100644 --- a/content/docs/1.39/operator.md +++ b/content/docs/1.39/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1301,7 +1301,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.40/deployment.md b/content/docs/1.40/deployment.md index 7a01985e..5736af58 100644 --- a/content/docs/1.40/deployment.md +++ b/content/docs/1.40/deployment.md @@ -147,7 +147,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.40/operator.md b/content/docs/1.40/operator.md index f4cb5717..b7b97074 100644 --- a/content/docs/1.40/operator.md +++ b/content/docs/1.40/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.41/deployment.md b/content/docs/1.41/deployment.md index 6107d460..a07b3f0b 100644 --- a/content/docs/1.41/deployment.md +++ b/content/docs/1.41/deployment.md @@ -147,7 +147,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.41/operator.md b/content/docs/1.41/operator.md index f4cb5717..b7b97074 100644 --- a/content/docs/1.41/operator.md +++ b/content/docs/1.41/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.42/deployment.md b/content/docs/1.42/deployment.md index 6107d460..a07b3f0b 100644 --- a/content/docs/1.42/deployment.md +++ b/content/docs/1.42/deployment.md @@ -147,7 +147,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.42/operator.md b/content/docs/1.42/operator.md index f4cb5717..b7b97074 100644 --- a/content/docs/1.42/operator.md +++ b/content/docs/1.42/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.43/deployment.md b/content/docs/1.43/deployment.md index 0fb1cb5f..182cd3a3 100644 --- a/content/docs/1.43/deployment.md +++ b/content/docs/1.43/deployment.md @@ -150,7 +150,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.43/operator.md b/content/docs/1.43/operator.md index 1e9cb660..72418bb0 100644 --- a/content/docs/1.43/operator.md +++ b/content/docs/1.43/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.44/deployment.md b/content/docs/1.44/deployment.md index e90c3556..ad033fa0 100644 --- a/content/docs/1.44/deployment.md +++ b/content/docs/1.44/deployment.md @@ -150,7 +150,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through the agent. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.44/operator.md b/content/docs/1.44/operator.md index 1e9cb660..72418bb0 100644 --- a/content/docs/1.44/operator.md +++ b/content/docs/1.44/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.45/deployment.md b/content/docs/1.45/deployment.md index b6630ab1..67ebc307 100644 --- a/content/docs/1.45/deployment.md +++ b/content/docs/1.45/deployment.md @@ -150,7 +150,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.45/operator.md b/content/docs/1.45/operator.md index 10d5b868..a85551b7 100644 --- a/content/docs/1.45/operator.md +++ b/content/docs/1.45/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.46/deployment.md b/content/docs/1.46/deployment.md index b6630ab1..67ebc307 100644 --- a/content/docs/1.46/deployment.md +++ b/content/docs/1.46/deployment.md @@ -150,7 +150,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.46/operator.md b/content/docs/1.46/operator.md index 10d5b868..a85551b7 100644 --- a/content/docs/1.46/operator.md +++ b/content/docs/1.46/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.47/deployment.md b/content/docs/1.47/deployment.md index b6630ab1..67ebc307 100644 --- a/content/docs/1.47/deployment.md +++ b/content/docs/1.47/deployment.md @@ -150,7 +150,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.47/operator.md b/content/docs/1.47/operator.md index 10d5b868..a85551b7 100644 --- a/content/docs/1.47/operator.md +++ b/content/docs/1.47/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.48/deployment.md b/content/docs/1.48/deployment.md index b6630ab1..67ebc307 100644 --- a/content/docs/1.48/deployment.md +++ b/content/docs/1.48/deployment.md @@ -150,7 +150,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.48/operator.md b/content/docs/1.48/operator.md index 10d5b868..a85551b7 100644 --- a/content/docs/1.48/operator.md +++ b/content/docs/1.48/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.49/deployment.md b/content/docs/1.49/deployment.md index 2c81c96d..34668434 100644 --- a/content/docs/1.49/deployment.md +++ b/content/docs/1.49/deployment.md @@ -150,7 +150,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.49/operator.md b/content/docs/1.49/operator.md index 10d5b868..a85551b7 100644 --- a/content/docs/1.49/operator.md +++ b/content/docs/1.49/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.50/deployment.md b/content/docs/1.50/deployment.md index 2c81c96d..34668434 100644 --- a/content/docs/1.50/deployment.md +++ b/content/docs/1.50/deployment.md @@ -150,7 +150,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.50/operator.md b/content/docs/1.50/operator.md index 10d5b868..a85551b7 100644 --- a/content/docs/1.50/operator.md +++ b/content/docs/1.50/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.51/deployment.md b/content/docs/1.51/deployment.md index eba97593..ff773af8 100644 --- a/content/docs/1.51/deployment.md +++ b/content/docs/1.51/deployment.md @@ -150,7 +150,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.51/operator.md b/content/docs/1.51/operator.md index 10d5b868..a85551b7 100644 --- a/content/docs/1.51/operator.md +++ b/content/docs/1.51/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.52/deployment.md b/content/docs/1.52/deployment.md index 5782cca3..1635add7 100644 --- a/content/docs/1.52/deployment.md +++ b/content/docs/1.52/deployment.md @@ -150,7 +150,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.52/operator.md b/content/docs/1.52/operator.md index 10d5b868..a85551b7 100644 --- a/content/docs/1.52/operator.md +++ b/content/docs/1.52/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.53/deployment.md b/content/docs/1.53/deployment.md index 5782cca3..1635add7 100644 --- a/content/docs/1.53/deployment.md +++ b/content/docs/1.53/deployment.md @@ -150,7 +150,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.53/operator.md b/content/docs/1.53/operator.md index 10d5b868..a85551b7 100644 --- a/content/docs/1.53/operator.md +++ b/content/docs/1.53/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.54/deployment.md b/content/docs/1.54/deployment.md index 5782cca3..1635add7 100644 --- a/content/docs/1.54/deployment.md +++ b/content/docs/1.54/deployment.md @@ -150,7 +150,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.54/operator.md b/content/docs/1.54/operator.md index 10d5b868..a85551b7 100644 --- a/content/docs/1.54/operator.md +++ b/content/docs/1.54/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.55/deployment.md b/content/docs/1.55/deployment.md index 5782cca3..1635add7 100644 --- a/content/docs/1.55/deployment.md +++ b/content/docs/1.55/deployment.md @@ -150,7 +150,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.55/operator.md b/content/docs/1.55/operator.md index 10d5b868..a85551b7 100644 --- a/content/docs/1.55/operator.md +++ b/content/docs/1.55/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.56/deployment.md b/content/docs/1.56/deployment.md index 361e0cb5..be20c2a5 100644 --- a/content/docs/1.56/deployment.md +++ b/content/docs/1.56/deployment.md @@ -150,7 +150,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.56/operator.md b/content/docs/1.56/operator.md index 10d5b868..a85551b7 100644 --- a/content/docs/1.56/operator.md +++ b/content/docs/1.56/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/1.57/deployment.md b/content/docs/1.57/deployment.md index 361e0cb5..be20c2a5 100644 --- a/content/docs/1.57/deployment.md +++ b/content/docs/1.57/deployment.md @@ -150,7 +150,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/1.57/operator.md b/content/docs/1.57/operator.md index 10d5b868..a85551b7 100644 --- a/content/docs/1.57/operator.md +++ b/content/docs/1.57/operator.md @@ -858,16 +858,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1411,7 +1411,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/content/docs/next-release/deployment.md b/content/docs/next-release/deployment.md index f7ec613d..5e9e4333 100644 --- a/content/docs/next-release/deployment.md +++ b/content/docs/next-release/deployment.md @@ -150,7 +150,7 @@ When using gRPC, you have several options for load balancing and name resolution ### Agent level tags -Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=valuen`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. +Jaeger supports agent level tags, that can be added to the process tags of all spans passing through **jaeger-agent**. This is supported through the command line flag `--agent.tags=key1=value1,key2=value2,...,keyn=value`. Tags can also be set through an environment flag like so - `--agent.tags=key=${envFlag:defaultValue}` - The tag value will be set to the value of the `envFlag` environment key and `defaultValue` if not set. ## Collector diff --git a/content/docs/next-release/operator.md b/content/docs/next-release/operator.md index 55675134..134d4c6b 100644 --- a/content/docs/next-release/operator.md +++ b/content/docs/next-release/operator.md @@ -822,16 +822,16 @@ The following snippet shows the manual definition you can include in your `conta imagePullPolicy: IfNotPresent ports: - containerPort: 5775 - name: zk-compact-trft + name: zk-compact-thrift protocol: UDP - containerPort: 5778 name: config-rest protocol: TCP - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP - containerPort: 6832 - name: jg-binary-trft + name: jg-binary-thrift protocol: UDP - containerPort: 14271 name: admin-http @@ -1375,7 +1375,7 @@ Starting from version 1.16.0, the Jaeger Operator is able to generate spans rela - --reporter.grpc.host-port=dns:///jaeger-collector-headless.$(POD_NAMESPACE).svc.cluster.local:14250 ports: - containerPort: 6831 - name: jg-compact-trft + name: jg-compact-thrift protocol: UDP ``` diff --git a/scripts/cspell/project-words.txt b/scripts/cspell/project-words.txt index 7fe48453..69f8c5e5 100644 --- a/scripts/cspell/project-words.txt +++ b/scripts/cspell/project-words.txt @@ -125,13 +125,11 @@ telemtery thriftrw tolerations tracegen -trft uberctx unmarshaling upsample usercert userkey -valuen vlog volz weaveworks