#include <lbm.h>
Data Fields | |
| lbm_ulong_t | tr_dgrams_sent |
| lbm_ulong_t | tr_bytes_sent |
| lbm_ulong_t | tr_dgrams_rcved |
| lbm_ulong_t | tr_bytes_rcved |
| lbm_ulong_t | tr_dgrams_dropped_ver |
| lbm_ulong_t | tr_dgrams_dropped_type |
| lbm_ulong_t | tr_dgrams_dropped_malformed |
| lbm_ulong_t | tr_dgrams_send_failed |
| lbm_ulong_t | tr_src_topics |
| lbm_ulong_t | tr_rcv_topics |
| lbm_ulong_t | tr_rcv_unresolved_topics |
| lbm_ulong_t | lbtrm_unknown_msgs_rcved |
| lbm_ulong_t | lbtru_unknown_msgs_rcved |
| lbm_ulong_t | send_blocked |
| lbm_ulong_t | send_would_block |
| lbm_ulong_t | resp_blocked |
| lbm_ulong_t | resp_would_block |
| lbm_ulong_t | uim_dup_msgs_rcved |
| lbm_ulong_t | uim_msgs_no_stream_rcved |
| lbm_ulong_t lbm_context_stats_t_stct::tr_dgrams_sent |
Number of topic resolution datagrams sent from this context. Each datagram can contain one or more advertisements, queries, query responses, etc. from source or receiver objects. A faster accumulation of counts typically indicates more source, receiver, and/or context objects are being created.
| lbm_ulong_t lbm_context_stats_t_stct::tr_bytes_sent |
Number of topic resolution datagram bytes sent. This count is triggered under the same circumstances as tr_dgrams_sent (above), but measures the total number of bytes for all datagrams sent, including their headers.
| lbm_ulong_t lbm_context_stats_t_stct::tr_dgrams_rcved |
Number of topic resolution datagrams received by this context. Each datagram can contain one or more advertisements, queries, query responses, etc. from source or receiver objects. A faster accumulation of counts typically indicates more source, receiver, and/or context objects are being created.
| lbm_ulong_t lbm_context_stats_t_stct::tr_bytes_rcved |
Number of topic resolution datagram bytes received. This count is triggered under the same circumstances as tr_dgrams_rcved (above), but measures the total number of bytes for all datagrams received, including their headers.
| lbm_ulong_t lbm_context_stats_t_stct::tr_dgrams_dropped_ver |
Number of topic resolution datagrams discarded due to incorrect version. The datagram's version field must match the expectations of the receiving context.
| lbm_ulong_t lbm_context_stats_t_stct::tr_dgrams_dropped_type |
Number of topic resolution datagrams discarded due to incorrect type. The datagram's type field must match the expectations of the receiving context.
Number of topic resolution datagrams discarded due to being malformed or corrupted.
| lbm_ulong_t lbm_context_stats_t_stct::tr_dgrams_send_failed |
Number of topic resolution datagram sends that failed. This count should be at or at least near 0.
| lbm_ulong_t lbm_context_stats_t_stct::tr_src_topics |
Number of topics in the source topic resolver cache (also referred to as the topic map). Inordinately large or growing values here may impact performance.
| lbm_ulong_t lbm_context_stats_t_stct::tr_rcv_topics |
Total number of topics in the receiver topic resolver cache (also referred to as the topic map). Inordinately large or growing values here may impact performance.
Number of unresolved topics in the receiver topic resolver cache (aka topic map). Inordinately large or growing values here may impact performance, though this count can be close to the total number of topics in the resolver cache under normal conditions.
Number of LBT-RM datagrams received not belonging to any transport session. Such occurrences should be investigated. These datagrams can be from a source in a different topic resolution domain targeting the same group (or IP) and port as a source of interest on this receiver's topic resolution domain. Among less likely possibilities would be an attempt to spoof UM messages.
Number of LBT-RU datagrams received not belonging to any transport session. Such occurrences should be investigated. These datagrams can be from a source in a different topic resolution domain targeting the same group (or IP) and port as a source of interest on this receiver's topic resolution domain. Among less likely possibilities would be an attempt to spoof UM messages.
| lbm_ulong_t lbm_context_stats_t_stct::send_blocked |
Number of incidents where a UM send call was blocked. Unusually high counts could indicate performance degradation or I/O problems.
| lbm_ulong_t lbm_context_stats_t_stct::send_would_block |
Number of incidents where a UM send call returned EWOULDBLOCK. This is when a send call set to be nonblocking encounters an error condition where it would otherwise be blocked. Under normal operating conditions, this count should be at or near 0.
| lbm_ulong_t lbm_context_stats_t_stct::resp_blocked |
Number of incidents where a UM send response call was blocked. Unusually high counts could indicate performance degradation or I/O problems.
| lbm_ulong_t lbm_context_stats_t_stct::resp_would_block |
Number of incidents where a UM send response call returned EWOULDBLOCK. This is when a send response call set as nonblocking encounters an error condition where it would otherwise be blocked. Under normal operating conditions, this count should be at or near 0.
| lbm_ulong_t lbm_context_stats_t_stct::uim_dup_msgs_rcved |
Number of duplicate unicast immediate messages (UIMs) received and dropped.
Number of unicast immediate messages (UIMs) received without stream information.
1.5.2