This documentation is for WSO2 API Manager 2.1.0 View documentation for the latest release.
Message Tracing - API Manager 2.1.0 - WSO2 Documentation

All docs This doc
||
Skip to end of metadata
Go to start of metadata

Message Tracing refers to the process of identifying each message flow of each of the transactions that go through the Gateway. You can do message tracing on WSO2 API Manager by installing the Message Tracer feature that has been specifically developed for WSO2 products. You can use the Message Tracer to derive  logging, auditing, and debugging related information with regard to message content and it’s direction.

Message Tracer is a part of carbon-analytics. From API Manager 2.1.0 onward, the Message Tracer feature is built into WSO2 API Manager.

Configuring message tracing

Follow the steps below to configure the Message Tracer in API Manager to dump trace events to WSO2 APIM logs, which can be viewed via the terminal or the wso2carbon log file.

  1. Start the WSO2 API Manager server.
  2. Sign in to the WSO2 APIM Management Console (https://localhost:9443/carbon).
  3. Click Message Tracing, which is under the  Configure tab, to navigate to the Message Tracing Configurations.
  4. Select the following options to enable message tracing and click Update.

    ConfigurationDescription
    Dump Message ContentEnable Message tracing for the Content of the Message as well.
    Enable LoggingEnable Logging in the available logging handler in order to log the tracing message.
    Enable Analytics Event PublishingPublish tracing events to WSO2 API Manager Analytics

  5. Add an event publisher to log the trace messages in the APIM the wso2carbon log file.

    1. Go to Main > Event > Publishers and click Add Event Publisher.

    2. In Create a New Event Publisher page, add the following details and click Add Event Publisher.

      PropertyValue
      Event Publisher Namemessage_tracer_logger_publisher
      Event SourceDAS_MESSAGE_TRACE:1.0.0
      Stream Attributes

      Keep default values

      Output Event Adapter Typelogger
      Message Formattext

      Leave the Unique Identifier field blank.

After enabling message tracing, dump message content, and logging, you will see a log message similar to the following on the API Console/terminal for events such as API invocation etc.

[2018-07-17 17:42:41,140]  INFO - LoggerEventAdapter Unique ID: sample,
Event: meta_request_url:/sam/1.0/sd,
meta_host:172.18.0.1:9763,
meta_server:WSO2 API Manager,
correlation_activity_id:2835113514075786856680,
service_name:__SynapseService,
operation_name:mediate,
message_direction:IN,
soap_body:<soapenv:Body xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"/>,
soap_header:<soapenv:Header xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope"/>,
timestamp:1531829561138,
status:success,
username:,
transport-header-Host:172.18.0.1:8243,
transport-header-activityID:2835113514075786856680,
transport-header-User-Agent:curl/7.47.0,
transport-header-Accept:application/json,
transport-header-Authorization:Bearer ac48a3a7-9dd3-3461-a785-cbdf8c3a414c
[2018-07-17 17:42:41,140]  INFO - HandlerUtils Massage Info: Transaction id=2835113514075786856680  Message direction=IN  Server name=172.18.0.1:9763  Timestamp=1531829561138  Service name=__SynapseService  Operation Name=mediate
[2018-07-17 17:42:42,245]  INFO - LoggerEventAdapter Unique ID: sample,
 Event: meta_request_url:,
meta_host:172.18.0.1:9763,
meta_server:WSO2 API Manager,
correlation_activity_id:2835113514075786856680,
service_name:__SynapseService,
operation_name:mediate,
message_direction:OUT,
soap_body:<soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><jsonObject><hello>world</hello></jsonObject></soapenv:Body>,
soap_header:<soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"/>,
timestamp:1531829562245,
status:success,
username:,
transport-header-Via:1.1 vegur,
transport-header-activityID:2835113514075786856680,
transport-header-Content-Type:application/json,
transport-header-Date:Tue, 17 Jul 2018 12:12:41 GMT,
transport-header-Connection:keep-alive,
transport-header-Access-Control-Allow-Methods:GET,
transport-header-Access-Control-Allow-Origin:*,
transport-header-Access-Control-Allow-Headers:authorization,Access-Control-Allow-Origin,Content-Type,SOAPAction,
transport-header-Server:Cowboy,
transport-header-Content-Length:17
[2018-07-17 17:42:42,248]  INFO - HandlerUtils Massage Info: Transaction id=2835113514075786856680  Message direction=OUT  Server name=172.18.0.1:9763  Timestamp=1531829562245  Service name=__SynapseService  Operation Name=mediate

Publishing event tracing data to API Manager Analytics

As an additional step you can publish these trace messages to WSO2 API Manager Analytics server by following the steps below.

Before you begin,

Make sure you have configured API Manager Analytics. For more information, see Configuring APIM Analytics.

  1. Sign in to WSO2 APIM Management Console (https://localhost:9443/carbon) if you have not done so already.
  2. Select Enable Analytics Event Publishing, which is in the Message Tracing Configuration page and click Update.

    After you have saved the changes, WSO2 APIM will generate a stream definition in the <APIM_HOME>/repository/deployment/server/eventstreams/DAS_MESSAGE_TRACE_1.0.0.json file.

  3. Copy the DAS_MESSAGE_TRACE_1.0.0.json file and add it to the <APIM_ANALITICS_HOME>/repository/deployment/server/eventstreams directory to deploy the same definition in WSO2 API Manager Analytics.

  4. Start the WSO2 API Manager Analytics server.
  5. Sign in to WSO2 API Manager Analytics (https://localhost:9444/carbon).
  6. Persist the event stream so that the data is saved into a table.
    1. Navigate to Main > Event > Streams to view the available event streams.

      You will see the deployed stream under event streams. 

    2. Click the Edit option that is relevant to the stream definition DAS_MESSAGE_TRACE:1.0.0 file so that it opens in the edit view.
    3. Click Next[Persist Event] at the bottom of the edit view.
    4. In the next page select Persist Event Stream and select all the attribute check-boxes in order to persist all the information and click Save Event Stream.
  7. Add an Event receiver to point to the Event stream.
    1. Go to Main -> Event -> Receivers in WSO2 API Manager Analytics and click Add Event Receiver.
    2. Add the following details and click Add Event Receiver.

      PropertyValue
      Event Receiver Namemessage_trace_receiver
      Input Event Adapter Typewso2event
      Is events duplicated in clusterfalse
      Event StreamDAS_MESSAGE_TRACE:1.0.0
      Message formatwso2event

  8. Configure a publisher that can publish events to WSO2 API Manager Analytics.
    1. Sign in to WSO2 APIM Management console (https://localhost:9443/carbon) if you have not done so already.
    2. Go to Main > Event > Publishers and click Add Event Publisher.

    3. In Create a New Event Publisher page, add the following details and click Add Event Publisher.

      PropertyValue
      Event Publisher Namemessage_tracer_analytics_publisher
      Event SourceDAS_MESSAGE_TRACE:1.0.0
      Stream Attributes

      Keep default values

      Output Event Adapter Typewso2event
      Receiver URLtcp://localhost:7612
      User Nameadmin
      Passwordadmin
      Protocolthrift
      Publishing modenon-blocking
      Publishing Timeout0
      Message Formatwso2event

      Leave the Authenticator URL field blank.

If you have also enabled Analytics event Publishing in addition to enabling message tracing, dump message content, and logging, you can see the results in WSO2 API Manager Analytics by following the steps below:

  1. Sign in to the WSO2 API Manager Analytics Management Console (https://localhost:9444/carbon).
  2. Navigate to Main > Data Explorer.
  3. Select the table DAS_MESSAGE_TRACE and click Search.
    You will see the event data traced in the WSO2 Analytics Data Explorer as shown below.
  • No labels