Hi Jose,

First of all, I would like to Thank you for your contribution, and yes it's
very helpful.

Currently, we are also focusing on providing the distributed tracing for
APIM by OpenTracing <http://opentracing.io/> standard, and Praveen (cc'd)
here is working on that. Basically, with that, you are not restricted to
specific tracer and it lets users integrate with any servers that support
open tracing standard such as Zipkin, Jaeger, WSO2 SP, etc without having
tracer specific code.

Also, I would like to highlight as now APIM 2.5.0 is released, the APIM
Microgateway <https://docs.wso2.com/display/AM250/Microgateway+Quick+Start>
has default support to integrate with Zipkin with few steps. And I believe
it'll be very suitable for your microservices architecture.

Thanks,
Sinthuja.

On Mon, Jul 23, 2018 at 4:18 PM JOSE MARIA ALVAREZ FERNANDEZ <
[email protected]> wrote:

> Hi,
>
> We have been trying to build a module for WSO2 to work within a
> Microservice environment, and participate in a tracing context (in this
> case with Zipkin B3 Headers ->
> https://github.com/openzipkin/b3-propagation/blob/master/README.md)  and
> the result, although in beta, is here:
>
> https://github.com/jmalvarezf/wso2-zipkin-tracer
>
> We just wanted to know if that could be useful for you. Tracing is a great
> tool for a microservices environment, and in case you want to use WSO2 as
> the Api Manager, we find very important for the gateway to work within that
> context.
>
> The idea was to create an Axis2 module, and a handler, the first one to
> manage all the requests to the gateway, and the second to manage the API
> requests.
>
> Best regards,
>
> Jose Maria.
>
>
>
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Este mensaje, y en su caso, cualquier fichero anexo al mismo, puede
> contener información confidencial, siendo para uso exclusivo del
> destinatario, quedando prohibida su divulgación copia o distribución a
> terceros sin la autorización expresa del remitente. Si Vd. ha recibido este
> mensaje erróneamente, se ruega lo notifique al remitente y proceda a su
> borrado.
>
> Gracias por su colaboración.
>
> This message (including any attachments) may contain confidential
> information. It is intended for use by the recipient only. Any
> dissemination, copying or distribution to third parties without the express
> consent of the sender is strictly prohibited. If you have received this
> message in error, please delete it immediately and notify the sender.
>
> Thank you for your collaboration.
>
>
> -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>


-- 
*Sinthuja Rajendran*
Senior Technical Lead
WSO2, Inc.:http://wso2.com

Blog: http://sinthu-rajan.blogspot.com/
Mobile: +94774273955
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to