You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixes#445, #158
This PR addresses some Jaeger receiver config cleanup as well as makes some breaking changes to the way the config is handled. See below for details.
**Fixes/Updates**
- Disabled flag is respected per protocol
- Unspecified protocols will no longer be started
- Empty protocol configs can now be specified to start the protocol with defaults. e.g.
```
jaeger:
protocols:
grpc:
```
- Updated readmes
- Naming and behavior of per protocol Addr/Enabled functions in `trace_reciever.go` has been standardized.
- Added thrift tchannel test to meet code coverage
**Breaking Change**
Changed the way an empty `jaeger:` config is handled. An empty/default config does not start any jaeger protocols. Previously it started all three collector protocols. This is a consequence of not starting unspecified protocols.
Copy file name to clipboardExpand all lines: receiver/README.md
+9-14Lines changed: 9 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,32 +107,27 @@ This receiver receives traces in the [Jaeger](https://www.jaegertracing.io)
107
107
format. It translates them into the internal format and sends
108
108
it to processors and exporters.
109
109
110
-
It supports the Jaeger Collector protocols:
110
+
It supports the Jaeger Collector and Agent protocols:
111
+
- gRPC
111
112
- Thrift HTTP
112
113
- Thrift TChannel
113
-
- gRPC
114
+
- Thrift Compact
115
+
- Thrift Binary
114
116
115
-
By default, the Jaeger receiver supports all three protocols on the default ports
116
-
specified in [factory.go](jaegerreceiver/factory.go). The following demonstrates
117
-
how to specify the default Jaeger receiver.
117
+
By default, the Jaeger receiver will not serve any protocol. A protocol must be named
118
+
for the jaeger receiver to start. The following demonstrates how to start the Jaeger
119
+
receiver with only gRPC enabled on the default port.
118
120
```yaml
119
121
receivers:
120
122
jaeger:
123
+
protocols:
124
+
grpc:
121
125
```
122
126
123
-
It also supports the Jaeger Agent protocols:
124
-
- Thrift Compact
125
-
- Thrift Binary
126
-
127
-
By default, these services are not started unless an endpoint is explicitly defined.
128
-
129
127
It is possible to configure the protocols on different ports, refer to
130
128
[config.yaml](jaegerreceiver/testdata/config.yaml) for detailed config
131
129
examples.
132
130
133
-
// TODO Issue https://github.com/open-telemetry/opentelemetry-collector/issues/158
134
-
// The Jaeger receiver enables all protocols even when one is specified or a
135
-
// subset is enabled. The documentation should be updated when that fix occurs.
136
131
### Communicating over TLS
137
132
This receiver supports communication using Transport Layer Security (TLS), but only using the gRPC protocol. It can be configured by specifying a `tls-crendentials` object in the gRPC receiver configuration.
0 commit comments