Hi,
1. How a user will enable this? Is it through a configuration file? Is
it a runtime configuration?
2. Can a user turn on tracing for a particular queue/topic?
3. Will this be specific to MQTT or a generic one for AMQP/JMS queues?
-Chintana
On Thu, Jun 11, 2015 at 9:52 PM, Anuja Herath <[email protected]> wrote:
> Hi,
>
> We are in process of implementing message activity tracing feature for MB
> 3.0 . With enabling this implementation, it'll be possible to track the
> path and activities of each and every message. This will be useful to find
> root causes of message losses and delivery faults.
>
> For this we are implementing a separate Message Tracer class. So with
> that, it will be possible to enable Trace logs only for message activities.
>
> Below figure shows a sample message activity tracing scenario for a MQTT
> message.
>
> [image: Inline image 1]
> [image: Inline image 2]
>
>
> Thanks,
> Anuja.
>
> --
> Anuja Herath
> *Software Engineer*
> *WSO2, Inc.*
> Mobile : +94 (0)71 429 8861
>
> _______________________________________________
> Architecture mailing list
> [email protected]
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
--
Chintana Wilamuna
Solutions Architect
WSO2, Inc.; http://wso2.com
lean.enterprise.middleware
phone: +1 408 429 3321
blog: http://engwar.com/
linkedin: http://www.linkedin.com/in/chintanawilamuna
twitter: twitter.com/std_err
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
