In this document, it will explain how to use wso2 message tracer feature on the carbon-based product. Here we used message tracer feature 1.0.x versions as an example. Also, the document will explain how to install and configure message tracer on your wso2 product.
Message tracing is an identification of each message flow in each transaction which is going through message gateway.
Message tracing is used to debug, audit, logging and debug messages content and it’s the direction. This is very useful when you want to track all message and its flow of the same transaction.
Message tracer feature is part of the carbon-analytics and you can find the message tracer source code from here.
Message tracer can be installed into your wso2 product as a feature from feature repo.
You can use available feature repose based on the carbon-kernel platform.
For 4.2.x kernel: http://product-dist.wso2.com/p2/carbon/releases/turing/
For 4.4.x kernel: http://product-dist.wso2.com/p2/carbon/releases/wilkes/
Also, you can build the feature repose by yourself on your local setup and point feature repo location as the file path. Here the git location for the source https://github.com/wso2/carbon-feature-repository
Next, try to install feature on the product. Here i used the wso2 apim 2.0.0
After feature installation done, go to “Configure” -> “Message Tracing” section from the left menu
Check “Enable Message Tracing” option to enable message tracing and click update
Select following option as you desire to configure message tracer
Check “Enable BAM Event Publishing” option to enable DAS data publishing
In order to publish the event to DAS you should configure following configuration on APIM and DAS.
Event stream definition should be configured in DAS in order to receive an event.
Also, event stream should be persistent in order to save event on Tables.
Next APIM should configure for a publisher in order to publish an event to DAS
[2016-06-11 09:48:01,901] INFO - HandlerUtils Massage Info: Transaction id=1401719621988766713213 Message direction=IN Server name=172.16.2.136:9763 Timestamp=1465618681901 Service name=__SynapseService Operation Name=mediate
[2016-06-11 09:48:01,903] INFO - HandlerUtils Massage Info: Transaction id=1401719621988766713213 Message direction=OUT Server name=172.16.2.136:9763 Timestamp=1465618681903 Service name=__SynapseService Operation Name=mediate
[2016-06-11 09:48:01,909] INFO - HandlerUtils Massage Info: Transaction id=140172037238671183803 Message direction=IN Server name=172.16.2.136:9763 Timestamp=1465618681909 Service name=__SynapseService Operation Name=mediate
[2016-06-11 09:48:01,917] INFO - HandlerUtils Massage Info: Transaction id=140172037238671183803 Message direction=OUT Server name=172.16.2.136:9763 Timestamp=1465618681917 Service name=__SynapseService Operation Name=mediate