zipkin-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From abe...@apache.org
Subject [incubator-zipkin-website] 06/16: fixed case format of jaeger
Date Sun, 21 Apr 2019 21:02:30 GMT
This is an automated email from the ASF dual-hosted git repository.

abesto pushed a commit to branch sync-from-githubio
in repository https://gitbox.apache.org/repos/asf/incubator-zipkin-website.git

commit e646cb2c2dbcbc39f6afa54dd3b015f67cfb6df4
Author: Adrian Cole <adriancole@users.noreply.github.com>
AuthorDate: Fri Jan 4 07:57:01 2019 +0800

    fixed case format of jaeger
---
 pages/extensions_choices.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pages/extensions_choices.md b/pages/extensions_choices.md
index 878ac07..5dd6d10 100644
--- a/pages/extensions_choices.md
+++ b/pages/extensions_choices.md
@@ -41,7 +41,7 @@ Listed below are alternative backends that accept Zipkin format. Some use
the sa
    - When [zipkin-receiver](https://github.com/apache/incubator-skywalking/blob/master/docs/en/setup/backend/backend-receivers.md)
is enabled, Skywalking exposes the same HTTP POST endpoints Zipkin does
      - http port 9411 accepts `/api/v1/spans` (thrift, json) and `/api/v2/spans` (json, proto)
POST requests.
      - this extension uses the same encoding library and same endpoints as Zipkin does.
- - [jaeger](https://github.com/jaegertracing/jaeger)
+ - [Jaeger](https://github.com/jaegertracing/jaeger)
    - When `COLLECTOR_ZIPKIN_HTTP_PORT=9411` is set, Jaeger exposes a partial implementation
of Zipkin's HTTP POST endpoints
      - http port 9411 accepts `/api/v1/spans` (thrift, json) and `/api/v2/spans` (json, but
not proto) POST requests.
    - When `SPAN_STORAGE_TYPE=kafka` and `zipkin-thrift`, Jaeger reads Zipkin v1 thrift encoded
span messages from a Kafka topic.


Mime
View raw message