How to adjust the log level of nvds_msgbroker witht he python bindings

Accelerated Computing Intelligent Video Analytics DeepStream SDK
1

Please provide complete information as applicable to your setup.

• Hardware Platform (Jetson / GPU)
• DeepStream Version
• JetPack Version (valid for Jetson only)
• TensorRT Version
• NVIDIA GPU Driver Version (valid for GPU only)
• Issue Type( questions, new requirements, bugs)
• How to reproduce the issue ? (This is for bugs. Including which sample app is using, the configuration files content, the command line used and other details for reproducing)
• Requirement details( This is for new requirement. Including the module name-for which plugin or for which sample application, the function description)

Jetson Orin AGX 64 GB
Deepstream 6.4
Jetpack 6.0 DP

How can I ajdust the log-level of the message broker using the python bindings - is there a property somewhere that can be set to supress all the mqtt protocol log messages?

3

could you share some log which you don’t want to see? why do you need to reduce the log? for performance?

4

For example , all this:

[mosq_mqtt_log_callback] Client uniqueID sending PUBLISH (d0, q0, r0, m7626, 'test', ... (1731 bytes))
[mosq_mqtt_log_callback] Client uniqueID sending PUBLISH (d0, q0, r0, m7627, 'test', ... (1730 bytes))
[mosq_mqtt_log_callback] Client uniqueID sending PUBLISH (d0, q0, r0, m7628, 'test', ... (1729 bytes))
[mosq_mqtt_log_callback] Client uniqueID sending PUBLISH (d0, q0, r0, m7629, 'test', ... (1729 bytes))
[mosq_mqtt_log_callback] Client uniqueID sending PUBLISH (d0, q0, r0, m7630, 'test', ... (1727 bytes))
[mosq_mqtt_log_callback] Client uniqueID sending PUBLISH (d0, q0, r0, m7631, 'test', ... (1727 bytes))
[mosq_mqtt_log_callback] Client uniqueID sending PUBLISH (d0, q0, r0, m7632, 'test', ... (1728 bytes))
Publish callback with reason code: Success.
Publish callback with reason code: Success.
Publish callback with reason code: Success.
Publish callback with reason code: Success.
Publish callback with reason code: Success.
Publish callback with reason code: Success.
Publish callback with reason code: Success.

Main reason to supress some of this is readibility - its drowning out my other output.

5

Thank for the sharing! it is the low-level lib. currently there is no toggle to control the printing.

6

good to know! thanks.

Just out of curiosity - would there be any performance penalties or other reasons to use nvds_msgbroker over e.g. paho.mqtt?

7

it only prints some mqtt logs. it should not have performance issue. and this log is useful for check mqtt low-level issue.

8

got it- so there is still the question about using a different mqtt package - any thoughts?

9

nvmsgbroker plugin is opensource and the nvmsgbroker low-level is not opensource. you can customize the low-level lib. please find “new-api” in the doc.

10

got it- so there is still the question about using a different mqtt package - any thoughts?

11

Sorry for the late reply, Is this still an DeepStream issue to support? Thanks!

12

yes it is - maybe my question got lost in the thread, because it is still unanswered

would there be any performance penalties or other reasons to use nvds_msgbroker over e.g. paho.mqtt?

13

please refer to \opt\nvidia\deepstream\deepstream-6.4\sources\libs\mqtt_protocol_adaptor\README. Currently DeepStream is using this mosquitto version. we did not test other mqtt versions.

14

There is no update from you for a period, assuming this is not an issue anymore. Hence we are closing this topic. If need further support, please open a new one. Thanks