Open topic with navigation

# 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.

Endpoint
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

Transport
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

Note: Bytes sent and received need not correlate exactly with messages sent and received on corresponding endpoints. For example, filtering and optimizations can decouple these metrics.

## Queues

These metrics report activity in each individual event queue in a client.

ID | Metric Type | Description
--- | --- | ---
41 | Queue Backlog | Maximum number of messages in an event queue in the client during the sample interval.
42 | Queue Discards | Inbound messages discarded by a queue in the client.

## 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.

Multicast and RUDP Transports
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

Multicast Connection
ID | Metric Type | Description | Tracking
--- | --- | --- | ---
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 the TIBCO FTL documentation. | Per multicast sender

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO FTL® - Enterprise Edition

Copyright © 2009-2024. Cloud Software Group, Inc. All Rights Reserved.