Catalog of Application Metrics
These tables describe metrics that you can use to assess the operation of a client application or service.
TIBCO FTL software gathers metrics for clients (applications), event queues, transports, and endpoints. It can also gather metrics for subscribers, publishers, and connections.
Unless otherwise specified, a metric reports a counter's value at the end of each sample interval, and the counter resets to zero for the next interval.
Each data sample submessage contains a type field. Its value is one of the type ID numbers in these tables, denoting a metric type.
Application Metrics
These metrics measure the operation of a client.
| ID | Metric Type | Description |
|---|---|---|
| 51 | Dynamic Formats | Number of distinct dynamic formats registered within the client.
Creating a message with a dynamic format can increment this counter. Receiving an inbound message with a dynamic format can increment this counter. This counter can decrease as the client library automatically unregisters unused formats. |
| 70 | Resident Memory Set Size | Current size in kilobytes of an application's working memory set. |
| 71 | Peak Resident Memory Set Size | Maximum size in kilobytes, since the client started, of an application's working memory set. |
| 72 | Process VM | Current size in kilobytes of an application's virtual memory set. |
| 73 | User CPU Time | Total user CPU time in microseconds, that is, time executing the client's object code since the client started. |
| 74 | System CPU Time | Total system CPU time in microseconds, that is, time executing operating system calls from the client since the client started. |
| 75 | Total CPU Time | Total CPU time in microseconds, that is, the sum of time executing the client's object code and its operating system calls since the client started. |
Endpoint Metrics
These metrics report activity on an endpoint of a client.
| ID | Metric Type | Description | Tracking |
|---|---|---|---|
| 67 | Store Mismatch Messages | Number of message flows that result from persistence store mismatch.
Any non-zero value indicates a store mismatch misconfiguration. Store mismatch is a misconfiguration in which a direct path transport connects two endpoints that are associated with two different persistence stores. |
Per endpoint |
| 90011 | Endpoint Info | When the value of
type field is
90011, then the monitoring message describes an endpoint.
A monitoring message of this type always contains zero as its data (value field). That is, it does not report a metric. Instead, it contains information about a endpoint. You can correlate this information with metric messages with the same identifier in the context field. |
Per endpoint |
| 90012
(2) |
Endpoint Delivered Messages (Received) | Inbound data messages through an endpoint in the client.
Use ID 90012 for this metric. ID 2 is deprecated. |
Per endpoint |
| 90013
(1) |
Endpoint Published Messages (Sent) | Outbound data messages through an endpoint in the client.
Use ID 90013 for this metric. ID 1 is deprecated. |
Per endpoint |
| 90014 | Endpoint Non-Matching Messages | This metric counts the number of outbound messages that an endpoint did not transmit because they did match the content matcher of any remote subscriber. | Per endpoint |
| ID | Metric Type | Description | Tracking |
|---|---|---|---|
| 90015 | Subscriber Delivered Messages | Inbound data messages through a subscriber in the client. | Per subscriber |
| 90016 | Publisher Published Messages | Outbound data messages through a publisher in the client. | Per publisher |
| 90017 | Publisher Non-Matching Messages | Outbound data messages that a publisher did not transmit because they did not match the content matcher of any remote subscriber. | Per publisher |
| ID | Metric Type | Description | Tracking |
|---|---|---|---|
| 12 | Bytes Received | Inbound data bytes on a transport in the client. | Per transport |
| 11 | Bytes Sent | Outbound data bytes on a transport in the client. | Per transport |
| 31 | Data Lost | Inbound data loss events on a transport in the client.
It is not possible to measure the magnitude of the events in bytes. |
Per transport |
| 32 | Format Unavailable | Messages with an unrecognized format carried on a transport in the client. | Per transport |
| ID | Metric Type | Description | Tracking |
|---|---|---|---|
| 90001 | Connection Info | When the value of
type field is
90001, then the monitoring message describes a connection.
A monitoring message of this type always contains zero as its data (value field). That is, it does not report a metric. Instead, it contains information about a connection. You can correlate this information with metric messages with the same identifier in the context field.
|
Per connection |
| 90002 | Receiver-Side Matches | The number of inbound messages that matched a content matcher at the receive side of a connection.
When the send side of a transport does not have complete content matcher interest for all its subscribers, it temporarily sends all messages, and the receive side of the transport applies content matching. Each successful match increments this metric once per message. When complete content matcher interest is available at the send side of a transport, the receive side does not increment this metric. |
Per connection |
| 90003 | Receiver-Side Discards | The number of inbound messages discarded at the receiver side of a connection because they did not match the content matcher of any subscriber.
Discard could occur because the interested subscriber has closed. Discard could occur when the send side of a transport does not have complete content matcher interest for all its subscribers. |
Per connection |
| 90004 | Null Matches | The number of inbound messages that a connection delivered to subscribers with null content matchers. | Per connection |
| 90005 | Connection Bytes Sent | The number of outbound bytes on a connection. | Per connection |
| 90006 | Connection Bytes Received | The number of inbound bytes on a connection. | Per connection |
| 90007 | Connection Messages Sent with Matching Fields | The number of outbound messages with matchable fields on a connection.
(Opaque messages do not have matchable fields.) |
Per connection |
| 90008 | Connection Messages Sent Opaque | The number of outbound opaque messages on a connection.
(Opaque messages do not have matchable fields.) |
Per connection |
| 90009 | Connection Received Matching | The number of inbound messages on a connection that matched a subscriber's content matcher.
The messages arrived at the receiver connection because the sender detected interest in them using a content matcher. That content matcher is in the matcher-string field of the monitoring data sample submessage. If a message matches the content matchers of multiple subscribers, then the receiver connection increments the counter corresponding to each matching subscriber. Each monitoring data sample submessage indicates its subscriber in the fields endpoint_name, endpoint_mon_id, and (when available) subscriber_label. |
Per connection |
| 90010 | Connection Sent Matching | The number of outbound messages that matched a remote subscriber's content matcher. That content matcher is in the matcher-string field of the monitoring data sample submessage. | Per connection |
| 90018 | Connection Packets Sent | The number of outbound packets on a connection. | Per connection |
| 90019 | Connection Packets Received | The number of inbound packets on a connection. | Per connection |
| 90020 | Connection Packets Retransmitted | The number of outbound packets retransmitted on a connection.
If the connection retransmits a packet several times, it increments this counter for each retransmission. |
Per connection |
| 90021 | Connection Packets Missed | The number of missed inbound packets on an RUDP connection. | Per connection |
| 90022 | Connection Packets Lost Outbound | The number of outbound packets discarded on an RUDP connection. | Per connection |
| 90023 | Connection Packets Lost Inbound | The number of lost inbound packets on an RUDP connection.
The connection accounts a packet as lost after its reliability constraints expire. |
Per connection |
Metrics for Multicast and RUDP
TIBCO FTL software gathers additional metrics for transports and connections that use UDP-based protocols, such as multicast and RUDP transports.
Unless otherwise specified, a metric reports a counter's value at the end of each sample interval. Transport metrics are cumulative since the transport established its bus. Connection metrics are cumulative since the connection's start time.
| ID | Metric Type | Description | Tracking |
|---|---|---|---|
| 61 | Packets Sent | Outbound data packets on a multicast or RUDP transport.
This counter includes all outbound data packets, including original data packets and retransmitted data packets. |
Per transport |
| 62 | Packets Received | Inbound data packets on a multicast or RUDP transport.
This counter includes all inbound data packets, including original data packets and retransmitted data packets. |
Per transport |
| 63 | Packets Retransmitted | Outbound packets retransmitted on a multicast or RUDP transport.
If the transport retransmits a packet several times, it increments this counter for each retransmission. |
Per transport |
| 64 | Packets Missed | Number of missed inbound packets on a multicast or RUDP transport. | Per transport |
| 65 | Packets Lost Outbound | Number of outbound packets discarded on a multicast or RUDP transport. | Per transport |
| 66 | Packets Lost Inbound | Number of inbound packets deemed lost on a multicast or RUDP transport.
The transport accounts a packet as lost after its reliability constraints expire. |
Per transport |
| ID | Metric Type | Description | Tracking |
|---|---|---|---|
| 90021 | Connection Packets Missed | The number of missed inbound packets on an RUDP connection. | Per connection |
| 90022 | Connection Packets Lost Outbound | The number of outbound packets discarded on an RUDP connection. | Per connection |
| 90023 | Connection Packets Lost Inbound | The number of lost inbound packets on an RUDP connection.
The connection accounts a packet as lost after its reliability constraints expire. |
Per connection |
| ID | Metric Type | Description | Tracking |
|---|---|---|---|
| 90024 | Multicast Receiver Info | When the value of
type field is
90024, then the monitoring message describes a multicast receiver.
A monitoring message of this type always contains zero as its data (value field). That is, it does not report a metric. Instead, it contains information about a multicast receiver. You can correlate this information with metric messages with the same identifier in the context field. |
Per multicast receiver |
| 90025 | Multicast Sender Info | When the value of
type field is
90025, then the monitoring message describes a multicast sender.
A monitoring message of this type always contains zero as its data (value field). That is, it does not report a metric. Instead, it contains information about a multicast sender. You can correlate this information with metric messages with the same identifier in the context field. |
Per multicast sender |
| 90026 | Multicast Received Bytes | The number of inbound raw bytes that arrive on a multicast receiver. | Per multicast receiver |
| 90027 | Multicast Delivered Bytes | The number of inbound bytes that a multicast receiver reassembles into messages.
If the connection rejects a packet, it excludes the packet's bytes from this metric. |
Per multicast receiver |
| 90028 | Multicast Received Packets | The number of inbound raw packets on a multicast receiver. | Per multicast receiver |
| 90029 | Multicast Delivered Packets | The number of inbound packets that a multicast receiver reassembles into messages.
If the connection rejects a packet, it excludes the packet from this metric. |
Per multicast receiver |
| 90030 | Multicast Sent Packets | The number of UDP protocol packets that an individual multicast receiver sends (upstream) to its multicast sender. | Per multicast receiver |
| 90031 | Multicast Sent NAK Requests | The number of retransmission request packets that a multicast receiver has sent. | Per multicast receiver |
| 90032 | Multicast Sent NAKs | The number of packets for which a multicast receiver has requested retransmission.
(If a receiver requests retranmission of the same packet multiple times, it increments this counter each time.) |
Per multicast receiver |
| 90033 | Multicast Lost Packets | The number of lost inbound packets at an individual multicast receiver.
The receiver accounts a packet as lost after its reliability constraints expire. |
Per multicast receiver |
| 90034 | Multicast Duplicate Received Packets | The number of duplicate inbound packets at an individual multicast receiver. | Per multicast receiver |
| 90035 | Multicast Data Errors | The number of corrupt inbound packets at an individual multicast receiver. | Per multicast receiver |
| 90036 | Multicast Sender Packets Sent | The number of outbound data packets from an individual multicast sender. | Per multicast sender |
| 90037 | Multicast Sender Bytes Sent | The number of outbound data bytes from an individual multicast sender. | Per multicast sender |
| 90038 | Multicast Sender Packets Retransmitted | The number of times that an individual multicast sender retransmitted an outbound data packet. | Per multicast sender |
| 90039 | Multicast Sender Packets Lost Outbound | The number of data packets that an individual multicast sender discards, resulting in data loss. | Per multicast sender |
| 90040 | Send Backlog Maximum Size | The largest data backlog (in bytes) during this monitoring interval (not cumulative).
(For background information see "Send: Blocking versus Non-Blocking" in TIBCO FTL Development.) |
Per multicast sender |