You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@zipkin.apache.org by ad...@apache.org on 2019/05/10 00:52:55 UTC
[incubator-zipkin-website] branch master updated: Update Pitchfork
extension to mention Kafka and RabbitMq (#9)
This is an automated email from the ASF dual-hosted git repository.
adriancole pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/incubator-zipkin-website.git
The following commit(s) were added to refs/heads/master by this push:
new 72780f6 Update Pitchfork extension to mention Kafka and RabbitMq (#9)
72780f6 is described below
commit 72780f6a7878d84bf0ce37654fcab6d61ea667b3
Author: worldtiki <dm...@hotels.com>
AuthorDate: Fri May 10 01:52:51 2019 +0100
Update Pitchfork extension to mention Kafka and RabbitMq (#9)
Co-Authored-By: worldtiki <wo...@gmail.com>
---
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 5dd6d10..412d00e 100644
--- a/pages/extensions_choices.md
+++ b/pages/extensions_choices.md
@@ -47,7 +47,7 @@ Listed below are alternative backends that accept Zipkin format. Some use the sa
- 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
+ - Pitchfork exposes the same HTTP POST endpoints Zipkin does. It can also consume spans from a Kafka topic or a RabbitMQ queue.
- 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