Skip to main content
Top
Review meshIQ Products (G2.com)

Universal Messaging Metric Streaming

This project streams metrics from the Integration Server, as well as metrics related to Universal Messaging such as channels, durables, and queues, into meshIQ Track. These metrics can be analyzed in Autopilot as facts.

Importing the meshIQ Universal Messaging Project into the Integration Server Console

  1. Download the attachment MeshiqUMMetrics_11.2.0.zip and extract its contents.
  2. Place the extracted data into one of the following paths, depending on what exists on your disk:
    • IntegrationServer/instances/default/replicate/inbound or
    • IntegrationServer/replicate/inbound
  3. Log into the Integration Server Console (e.g., http://<hostip>:5555) with your credentials.
  4. The following page can be seen after the login.
    UM1.png
  5. From the panel present on the left side, select Packages>Management.
  6. Click the Install Inbound Releases option under the management. Please refer the screenshot below.
    Universal messaging screenshot.png
  7. Once the installation is complete, go back to Packages on the left-side panel.
  8. Select the package name MeshiqUMMetrics_11.2.0 in the main panel to access its services.
  9. To check if the Integration Server provides metrics are exposed as JSON over HTTP, use a URL formatted like this:
    http://<hostip>:5555/rad/rad:allMetricsData/allMetricsData/<realmHost>/<realmPort> 
    The realmHost, Port number, realmPort are subject to change depending on your environment. For example:
    http://localhost:5555/rad/rad:allMetricsData/allMetricsData/localhost/9000.

Running TNT4J-Streams to Stream Data into Track

  • Download the streams folder (Path where the zip file is located) from the ftp site.
  • Extract the zip file.
  • Navigate to the um-metrics folder:
    Streams\tnt4j-streams-2.4-SNAPSHOT\samples\um-metrics 
  • You will find four files: run.bat, run.sh, parsers.xml, and tnt-data-source.xml.
  • In the parsers.xml file, all the fields that need to be streamed like published, consumed, total connections are mentioned.
  • In the tnt-data-source.xml file, specify the path of the sink to which the data will be streamed. Within this file Enter the IP of the track server (path of the sink to which the data will be streamed) and provide the streaming token in the following properties as mentioned below:

    <property name="event.sink.factory.EventSinkFactory.xray.Url" value="https://streams.meshiq.com"/>

     <property name="event.sink.factory.EventSinkFactory.xray.Token" value="DefaultToken"/>

  • Open the command prompt from the location where the um-metrics folder is placed.

  • Execute the command run.bat

  • All Integration Server metrics and Universal Messaging metrics will be streamed into the track UI in the form of snapshots.
  • To verify all the snapshot fields, execute the following JKQL query:

    “Get snapshot fields all”

  • Data can be viewed in various graphical formats. Here are some examples of graphs plotted using the metrics data.
    All Metrics Viewlets.jpg

Track Dashboard with um-metrics Data

Comparison table of published and consumed.jpg

Col chart showing Comparison between Published and Consumed Metrics. 

Total Connections Metrics.jpg

Bar chart plotted between total connections and snapshot names.

Comparison of data using linechart.jpg

Line chart Plotted for Published, Consumed and Snapshot names data.

Analyzing the Data in Autopilot:

  • The same data is also available in Autopilot, displayed as facts.
  • When you expand the um-metrics field, all the facts will be visible along with the corresponding metrics data in the below format.
    image (2).png

  • The following guide includes a section on the deployment process wrapper, which explains how to deploy an expert for universal messaging to view the streamed facts.