zipkin-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From abe...@apache.org
Subject [incubator-zipkin-website] 05/16: Add pitchfork to extension choices
Date Sun, 21 Apr 2019 21:02:29 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 a0f55f357cd5b2fb0c0e88fc9cce291b7341caf3
Author: Daniel Albuquerque <dmartinsalbuqu@hotels.com>
AuthorDate: Thu Jan 3 15:01:21 2019 +0000

    Add pitchfork to extension choices
---
 pages/extensions_choices.md | 12 +++++++-----
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/pages/extensions_choices.md b/pages/extensions_choices.md
index a90a02a..878ac07 100644
--- a/pages/extensions_choices.md
+++ b/pages/extensions_choices.md
@@ -39,14 +39,16 @@ Listed below are alternative backends that accept Zipkin format. Some
use the sa
     
  - [Apache SkyWalking](https://github.com/apache/incubator-skywalking)
    - 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.
+     - 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)
    - 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.
+     - 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.
      - Note: The above is a [deprecated practice](https://github.com/openzipkin/zipkin/tree/master/zipkin-collector/kafka#legacy-encoding)
in Zipkin. Most instrumentation bundle multiple spans per message in v2 format.
-
+ - [Pitchfork](https://github.com/HotelsDotCom/pitchfork)
+   - Pitchfork 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.
 
 Did we miss a server extension or alternative? Please open a pull-request to
 [openzipkin.github.io](https://github.com/openzipkin/openzipkin.github.io).


Mime
View raw message