We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
address: 0.0.0.0:8888
address: 0.0.0.0:8889
expvar
port: 27777
healthcheckv2
endpoint: "0.0.0.0:13133"
The text was updated successfully, but these errors were encountered:
I did some updates to the docs per : #751
The following seem to still be in the v1 docs and I believe should be somewhere in v2 docs, let me know what you think:
At default settings **jaeger-collector** exposes the following ports: | Port | Protocol | Endpoint | Function | ----- | ------- | -------- | ---- | 4317 | gRPC | n/a | Accepts traces in [OpenTelemetry OTLP format][otlp] (Protobuf). | 4318 | HTTP | `/v1/traces` | Accepts traces in [OpenTelemetry OTLP format][otlp] (Protobuf and JSON). | 14268 | HTTP | `/api/sampling` | Serves sampling policies (see [Remote Sampling](../sampling/#remote-sampling)). | | | `/api/traces` | Accepts spans in [jaeger.thrift][jaeger-thrift] format with `binary` thrift protocol (`POST`). | 9411 | HTTP | `/api/v1/spans` and `/api/v2/spans` | Accepts Zipkin spans in Thrift, JSON and Proto (disabled by default). | 14250 | gRPC | n/a | Used by **jaeger-agent** to send spans in [model.proto][] Protobuf format.
Sorry, something went wrong.
yes, those ports would still be relevant (sometimes the ports might be different)
jkowall
No branches or pull requests
address: 0.0.0.0:8888
(address: 0.0.0.0:8889
for ingester)expvar
extension:port: 27777
healthcheckv2
extension:endpoint: "0.0.0.0:13133"
The text was updated successfully, but these errors were encountered: