Data Flow of Monitoring Data and Log Messages

The following diagram illustrates the flow of FTL monitoring data and log messages.

Figure 73: Monitoring data and log flow

Explanation of the Diagram

  1. All data begins in clients. The FTL client library monitors the metrics relevant to each client. It forwards monitoring data, log messages, and advisory messages to the TIBCO FTL server.

  2. When the FTL server receives log messages or advisory messages from any of its clients, the FTL server immediately publishes those messages on the logging stream. Any FTL application can subscribe to the built-in logging endpoint to receive the logging stream.

  3. When the FTL server receives monitoring data from any of its clients, the FTL server immediately publishes that data on the monitoring stream. Any FTL application can subscribe to the built-in monitoring endpoint to receive the monitoring stream.

  4. The FTL server retains only the most recent value of each metric and the most recent log from each client. These values are available from the FTL server through its web API and administrative GUI. You can develop custom monitoring applications that subscribe to these streams and use their data.

  5. tibmongateway (or Monitoring scripts) from TIBCO® Messaging Monitor for TIBCO FTL® subscribes to both the monitoring stream and the logging stream, and stores the data in an InfluxDB database. InfluxDB is an open-source database. You can access the data directly from InfluxDB, or using other tools that manipulate and display the data, for example, Grafana.

  6. REST requests can be sent from the web browser, via the FTL Server, to retrieve log entries.