humble monitor error

[iceriver97]

ice@ice:~/下载/fasttest$ ./install/fastdds_monitor/bin/fastdds_monitor 
Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations.
2025-12-12 16:18:36.137 [BACKEND_DATABASE_QUEUE Error] endpoint 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.62 discovered on Participant 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.c1 but there is no such Participant in the database -> Function process_sample
2025-12-12 16:18:36.137 [BACKEND_DATABASE_QUEUE Error] endpoint 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.2.62 discovered on Participant 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.c1 but there is no such Participant in the database -> Function process_sample
2025-12-12 16:18:36.138 [BACKEND_DATABASE_QUEUE Error] endpoint 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.4.62 discovered on Participant 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.c1 but there is no such Participant in the database -> Function process_sample
2025-12-12 16:18:36.138 [BACKEND_DATABASE_QUEUE Error] endpoint 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.8.62 discovered on Participant 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.c1 but there is no such Participant in the database -> Function process_sample
2025-12-12 16:18:36.138 [BACKEND_DATABASE_QUEUE Error] endpoint 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.10.62 discovered on Participant 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.c1 but there is no such Participant in the database -> Function process_sample
2025-12-12 16:18:36.139 [BACKEND_DATABASE_QUEUE Error] endpoint 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.20.62 discovered on Participant 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.c1 but there is no such Participant in the database -> Function process_sample
2025-12-12 16:18:36.140 [BACKEND_DATABASE_QUEUE Error] endpoint 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.80.62 discovered on Participant 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.c1 but there is no such Participant in the database -> Function process_sample
2025-12-12 16:18:36.140 [BACKEND_DATABASE_QUEUE Error] endpoint 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.1.0.62 discovered on Participant 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.c1 but there is no such Participant in the database -> Function process_sample
2025-12-12 16:18:36.141 [BACKEND_DATABASE_QUEUE Error] endpoint 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.2.0.62 discovered on Participant 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.c1 but there is no such Participant in the database -> Function process_sample
2025-12-12 16:18:36.141 [BACKEND_DATABASE_QUEUE Error] endpoint 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.4.0.62 discovered on Participant 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.c1 but there is no such Participant in the database -> Function process_sample
2025-12-12 16:18:36.142 [BACKEND_DATABASE_QUEUE Error] endpoint 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.8.0.62 discovered on Participant 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.c1 but there is no such Participant in the database -> Function process_sample
2025-12-12 16:18:36.143 [BACKEND_DATABASE_QUEUE Error] endpoint 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.40.62 discovered on Participant 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.c1 but there is no such Participant in the database -> Function process_sample
2025-12-12 16:18:36.143 [BACKEND_DATABASE_QUEUE Error] endpoint 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.80.0.62 discovered on Participant 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.c1 but there is no such Participant in the database -> Function process_sample
2025-12-12 16:18:36.144 [BACKEND_DATABASE_QUEUE Error] endpoint 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.10.0.62 discovered on Participant 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.c1 but there is no such Participant in the database -> Function process_sample
2025-12-12 16:18:36.144 [BACKEND_DATABASE_QUEUE Error] endpoint 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.20.0.62 discovered on Participant 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.c1 but there is no such Participant in the database -> Function process_sample
2025-12-12 16:18:36.145 [BACKEND_DATABASE_QUEUE Error] endpoint 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.40.0.62 discovered on Participant 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.c1 but there is no such Participant in the database -> Function process_sample
2025-12-12 16:18:36.145 [BACKEND_DATABASE_QUEUE Error] endpoint 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|1.0.0.62 discovered on Participant 01.0f.9e.ab.48.e0.ec.8e.00.00.00.00|0.0.1.c1 but there is no such Participant in the database -> Function process_sample

版本信息如下：
fastcdr: v1.0.28
fastdds: v2.6.10
fastdds_monitor: v1.2.0
fastdds_statistics_backend: v0.7.0
foonathan_memory_vendor: v1.2.0
rmw_fastrtps: humble
profile如下：

<?xml version="1.0" encoding="UTF-8" ?>
<profiles xmlns="http://www.eprosima.com/XMLSchemas/fastRTPS_Profiles">

    <transport_descriptors>
        <!-- shared memory transport descriptor -->
        <transport_descriptor>
            <transport_id>shm_transport</transport_id>
            <type>SHM</type>
            <segment_size>214857600</segment_size> <!-- 100MB 214857600 -->
            <maxMessageSize>214857600</maxMessageSize> <!-- 2MB 214857600 -->
        </transport_descriptor>

        <!-- udp transport descriptor -->
        <transport_descriptor>
            <transport_id>udp_transport</transport_id>
            <type>UDPv4</type>
            <!--non_blocking_send>true</non_blocking_send--> <!-- yes, non-blocking, message lates is meaningless -->
            <!--sendBufferSize>130000</sendBufferSize-->  <!-- 2 max message -->
            <!--receiveBufferSize>130000</receiveBufferSize--> <!-- 2 max message -->
            <!--maxMessageSize>1470</maxMessageSize--> <!-- fastrtps allowed max -->
	    <!--output_port>5101</output_port-->
            <TTL>200</TTL>
            <interfaceWhiteList>
                    <address>127.0.0.1</address>
            </interfaceWhiteList>
        </transport_descriptor>
    </transport_descriptors>

    <participant profile_name="SHMParticipant" is_default_profile="true">
        <rtps>
            <propertiesPolicy>
                <properties>
                    <!-- Activate Fast DDS Statistics Module -->
                    <property>
                        <name>fastdds.statistics</name>
                        <value>HISTORY_LATENCY_TOPIC;NETWORK_LATENCY_TOPIC;PUBLICATION_THROUGHPUT_TOPIC;SUBSCRIPTION_THROUGHPUT_TOPIC;RTPS_SENT_TOPIC;RTPS_LOST_TOPIC;HEARTBEAT_COUNT_TOPIC;ACKNACK_COUNT_TOPIC;NACKFRAG_COUNT_TOPIC;GAP_COUNT_TOPIC;DATA_COUNT_TOPIC;RESENT_DATAS_TOPIC;SAMPLE_DATAS_TOPIC;PDP_PACKETS_TOPIC;EDP_PACKETS_TOPIC;DISCOVERY_TOPIC;PHYSICAL_DATA_TOPIC</value>
                    </property>
                </properties>
            </propertiesPolicy>
            <!-- Link the Transport Layer to the Participant -->
            <userTransports>
                <transport_id>shm_transport</transport_id>
                <transport_id>udp_transport</transport_id>
            </userTransports>
            <useBuiltinTransports>false</useBuiltinTransports>
        </rtps>
    </participant>

    <data_writer profile_name="default_writer_profile" is_default_profile="true">
	    <topic>
		    <historyQos>
			    <kind>KEEP_LAST</kind>
			    <depth>10</depth>
		    </historyQos>
	    </topic>
        <!-- Enable pull mode -->
        <propertiesPolicy>
            <properties>
                <property>
                    <name>fastdds.push_mode</name>
                    <value>false</value>
                </property>
            </properties>
        </propertiesPolicy>
        <qos>
            <publishMode>
                <kind>ASYNCHRONOUS</kind>
            </publishMode>
            <reliability>
                <!-- <kind>BEST_EFFORT</kind> -->
                <kind>RELIABLE</kind>
            </reliability>
            <durability>
                <kind>TRANSIENT_LOCAL</kind>
            </durability>
            <!-- <data_sharing>
                <kind>AUTOMATIC</kind>
            </data_sharing> -->
        </qos>
		<historyMemoryPolicy>PREALLOCATED_WITH_REALLOC</historyMemoryPolicy>
        <!-- <historyMemoryPolicy>DYNAMIC</historyMemoryPolicy> -->
    </data_writer>

    <data_reader profile_name="default_reader_profile" is_default_profile="true">
	    <topic>
		    <historyQos>
			    <kind>KEEP_LAST</kind>
			    <depth>100</depth>
		    </historyQos>
	    </topic>
	    <qos>
            <reliability>
                <!-- <kind>BEST_EFFORT</kind> -->
                <kind>RELIABLE</kind>
            </reliability>
            <durability>
                <kind>TRANSIENT_LOCAL</kind>
            </durability>
            <!-- <data_sharing>
                <kind>AUTOMATIC</kind>
            </data_sharing> -->
        </qos>
	    <historyMemoryPolicy>PREALLOCATED_WITH_REALLOC</historyMemoryPolicy>
        <!-- <historyMemoryPolicy>DYNAMIC</historyMemoryPolicy> -->
    </data_reader>
</profiles>

我想请问为什么没有针对 fastdds: v2.6.x 的monitor版本，rmw_fastrtps_humble要求必须使用v2.6.x，humble怎么使用monitor进行监控呢？现在现象就是我在当前工作目录下，分别source并运行talker/listener，想通过monitor查看统计信息，发现打开monitor监控对应domain的一瞬间就会报错，且统计信息也会戛然而止，不会再更新：

[iceriver97]

本地验证实际跟fastrtps_profile.xml配置相关，请问应该如何配置避免冲突呢？

[iceriver97]

长时间运行之后，throughput 突然没有数据，点击reset chart room 之后，Y轴出现inf及nan，终端不断打印：

Ignored NaN, Inf, or -Inf value.
Attempting to set invalid range for value axis: [ nan  -  nan ]

[iceriver97]

data_count 长时间为0，当我重新执行ros2 topic bw /xxx，会有一个突变，然后再变为0

[iceriver97]

其中50多秒没有data_count意味着什么?