[{"data":1,"prerenderedAt":261},["ShallowReactive",2],{"blog-post-zh-nanomq-newsletter-202209":3},{"post":4,"translationPath":260},{"id":5,"title":6,"author":7,"body":8,"cover":242,"coverHeight":243,"coverWidth":244,"date":245,"description":246,"draft":247,"extension":248,"meta":249,"navigation":250,"path":251,"pinned":247,"seo":252,"sitemap":253,"stem":256,"tags":257,"__hash__":259},"blog_zh\u002Fzh\u002Fblog\u002Fnanomq-newsletter-202209.md","新增桥接连接状态监控、重构日志系统",null,{"type":9,"value":10,"toc":230},"minimark",[11,23,27,36,46,49,53,71,74,84,87,93,96,102,105,109,112,118,121,124,127,133,136,139,142,145,151,155,158,215,224,227],[12,13,14,15,22],"p",{},"9 月，NanoMQ 继续保持稳步更新，最新的 ",[16,17,21],"a",{"href":18,"rel":19},"https:\u002F\u002Fgithub.com\u002Fnanomq\u002Fnanomq\u002Freleases\u002Ftag\u002F0.12.1",[20],"nofollow","0.12.1 版本","已于近日正式发布。此版本依旧带来了丰富的更新：桥接功能中增加了上下线事件和连接状态监控能力；重构升级了原有的日志系统；配置文件得到了简化，将多个配置文件合并整理为统一的单一文件。",[24,25,26],"h2",{"id":26},"桥接连接状态事件消息",[12,28,29,30,35],{},"IoT 应用中，弱网状态下时常出现网络不稳定的情况，需要一个可靠的途径来侦测当前设备的联网状态以及与云端的连通性。为此，NanoMQ 提供了利用桥接连接来探测网络连接状态的能力。当用户在边缘侧使用 NanoMQ 桥接到云端时，NanoMQ 会创建一个 ",[16,31,34],{"href":32,"rel":33},"https:\u002F\u002Fwww.emqx.com\u002Fzh\u002Fblog\u002Fthe-easiest-guide-to-getting-started-with-mqtt",[20],"MQTT"," 连接到指定的云端 Broker，基于 MQTT 的长连接特性，本地网络里的设备可以利用此连接来判断网络状态。",[12,37,38],{},[39,40],"img",{"alt":41,"src":42,"title":43,"width":44,"height":45},"桥接 MQTT","\u002Fimages\u002Fblog\u002Fzh\u002Fnanomq-newsletter-202209\u002F01.webp","网络侦测：桥接连接状态消息",1520,1171,[12,47,48],{},"如上图所示，当本地网络中断或其他故障导致桥接连接断开时，NanoMQ 会检测到桥接连接断开的情况，并将其转化为一个客户端上下线事件消息发布到系统主题中。网络恢复后桥接连接自动重连，也会发布一个上线事件消息到系统主题。本地的客户端和其他服务可以根据收到的此消息进行对应的应急处理，还可以配置多个桥接目标来作为备选服务避免因为云端服务中断导致的误判。",[50,51,52],"h3",{"id":52},"如何获取桥接上下线事件消息",[12,54,55,56,61,62,66,67,70],{},"目前 NanoMQ 的桥接状态事件支持所有的桥接方式，包括 MQTT 3.1.1\u002F5.0 和 MQTT over ",[16,57,60],{"href":58,"rel":59},"https:\u002F\u002Fwww.emqx.com\u002Fzh\u002Fblog\u002Fquic-protocol-the-features-use-cases-and-impact-for-iot-iov",[20],"QUIC","。 上下线事件消息的系统主题分别为 ",[63,64,65],"code",{},"$SYS\u002Fbrokers\u002Fdisconnected"," 和 ",[63,68,69],{},"$SYS\u002Fbrokers\u002Fconnected","。事件消息同样也支持作为一个标准 Publish 消息被以 WebHook 的方式获取。这里以一个 MQTT over QUIC 桥接配置为例，示范如何获取桥接连接的上下线消息：",[12,72,73],{},"若桥接配置为(只摘录部分相关)：",[75,76,81],"pre",{"className":77,"code":79,"language":80},[78],"language-text","bridge.mqtt.emqx.clientid=quic_client\nbridge.mqtt.emqx.keepalive=5\nbridge.mqtt.emqx.quic_keepalive=120\nbridge.mqtt.emqx.clean_start=false\nbridge.mqtt.emqx.username=quic_bridge\nbridge.mqtt.emqx.password=passwd\n","text",[63,82,79],{"__ignoreMap":83},"",[12,85,86],{},"使用 NanoMQ 命令行工具订阅对应主题，那么当本地网络中断时，桥接断开就会触发：",[75,88,91],{"className":89,"code":90,"language":80},[78],"nanomq_cli sub --url mqtt-tcp:\u002F\u002Flocalhost:1883 -t '$SYS\u002Fbrokers\u002Fconnected'\nconnect_cb: mqtt-tcp:\u002F\u002Flocalhost:1883 connect result: 0\n$SYS\u002Fbrokers\u002Fconnected: {\"username\":\"quic_bridge\", \"ts\":1664277443551,\"proto_name\":\"MQTT\",\"keepalive\":5,\"return_code\":\"0\",\"proto_ver\":4,\"client_id\":\"quic_client\", \"clean_start\":0}\n",[63,92,90],{"__ignoreMap":83},[12,94,95],{},"那么当本地网络恢复时，桥接重连成功就会触发：",[75,97,100],{"className":98,"code":99,"language":80},[78],"nanomq_cli sub --url mqtt-tcp:\u002F\u002Flocalhost:1883 -t '$SYS\u002Fbrokers\u002Fdisconnected'\nconnect_cb: mqtt-tcp:\u002F\u002Flocalhost:1883 connect result: 0\n$SYS\u002Fbrokers\u002Fdisconnected: {\"username\":\"quic_bridge\",\"ts\":1664277394014,\"reason_code\":\"8b\",\"client_id\":\"quic_client\"}\n",[63,101,99],{"__ignoreMap":83},[12,103,104],{},"可见上下线事件消息中的客户端 ID 和用户名\u002F密码都与桥接配置中的一致，可以此来区分本地客户端和桥接客户端。目前桥接连接状态与普通 MQTT 客户端是共享同一个系统主题，NanoMQ 也考虑为桥接网络状态单独设立一个系统主题，以及作为云边消息总线加入标准的网络健康监控功能。欢迎广大用户提交相关 Issue 和功能申请。",[50,106,108],{"id":107},"新增-quic-传输层的-keep-alive-参数配置","新增 QUIC 传输层的 Keep Alive 参数配置",[12,110,111],{},"QUIC 内置了一个连接保持机制，为了让用户能够更细颗粒度的控制 MQTT 和 QUIC 的超时时间，NanoMQ 的桥接功能把两者的超时设置都暴露为可设置状态，后续还会开放更多的 QUIC 传输层参数供用户调优。",[75,113,116],{"className":114,"code":115,"language":80},[78],"## Ping: interval of a downward bridging connection via QUIC.\nbridge.mqtt.emqx.quic_keepalive=120\n",[63,117,115],{"__ignoreMap":83},[24,119,120],{"id":120},"配置文件简化",[12,122,123],{},"在 0.12 版本之前，NanoMQ 每个模块都有一个独立的配置文件，需要单独打开每个文件进行修改配置，启动较为繁琐。从0.12 版本开始，我们将正式统一合并所有的配置项到 nanomq.conf， 并且为每个模块单独增加了分组。",[12,125,126],{},"需要注意的是，之前的命令行参数中指定桥接配置文件和用户名密码文件路径的功能被废弃。",[75,128,131],{"className":129,"code":130,"language":80},[78],"  --bridge \u003Cpath>            The path of a specified bridge configuration file\n  --auth \u003Cpath>              The path of a specified authorize configuration file\n",[63,132,130],{"__ignoreMap":83},[12,134,135],{},"此修改不影响 ZeroMQ 网关的配置文件（nanomq_gatewaty.conf属于 nanomq_cli）和容器部署情况下通过环境变量指定配置文件的方式。",[24,137,138],{"id":138},"日志系统重构",[12,140,141],{},"NanoMQ 的旧有日志系统支持命令行、文件和 Syslog 三种模式，但是不能通过配置进行开关，不支持分级输出，而且需要在编译阶段通过修改 CMake 参数来启用，调试和运维分析有一定困难。在 0.12 版本我们重构了整个日志系统，保持对原有三种输出目标和 Syslog 标准兼容外，新增了 trace | debug | info | warn | error | fatal 5 种日志等级，以及指定日志文件路径和日志文件滚动更新等功能。",[12,143,144],{},"日志配置示例：",[75,146,149],{"className":147,"code":148,"language":80},[78],"## ------------------ Logging Config ------------------ ##\n## - file: 输出日志到文件\n## - console: 输出日志到命令行\n## - syslog: 输出日志到 syslog系统\n## Value: file | console | syslog 支持并列配置\nlog.to=file,console,syslog\n\n## Value: trace | debug | info | warn | error | fatal\n## 设置日志等级\n##\n## Default: warn\nlog.level=warn\n\n## 若配置了输出日志到文件，则在此指定文件路径\nlog.dir=\u002Ftmp\n\n## 若配置了输出日志到文件，则在此指定文件名\nlog.file=nanomq.log\n\n## 单个日志文件的最大大小，若超过则会滚动更新\n## 支持单位参数: KB | MB | GB\nlog.rotation.size=10MB\n\n## 最大保存的滚动更新的日志文件个数\nlog.rotation.count=5\n",[63,150,148],{"__ignoreMap":83},[24,152,154],{"id":153},"nanosdk-增加更多-api-封装","NanoSDK 增加更多 API 封装",[12,156,157],{},"此前 NanoSDK 的 API 多为 NNG 的风格，需要用户自己组装 MQTT 消息并发送来完成订阅和接触订阅的操作。从 NanoSDK 0.7.5 开始，NanoSDK 里新增了以下更方便、封装程度更高的 MQTT API：",[159,160,161,174],"table",{},[162,163,164],"thead",{},[165,166,167,171],"tr",{},[168,169,170],"th",{},"nng_mqtt_subscribe()",[168,172,173],{},"perform a subscribe request synchnously",[175,176,177,186,194,202],"tbody",{},[165,178,179,183],{},[180,181,182],"td",{},"nng_mqtt_subscribe_async()",[180,184,185],{},"perform a subscribe request asynchnously",[165,187,188,191],{},[180,189,190],{},"nng_mqtt_unsubscribe()",[180,192,193],{},"perform an unsubscribe request synchnously",[165,195,196,199],{},[180,197,198],{},"nng_mqtt_unsubscribe_async()",[180,200,201],{},"perform an unsubscribe request asynchnously",[165,203,204,207],{},[180,205,206],{},"nng_mqtt_disconnect()",[180,208,209,210],{},"Disconnect an ",[16,211,214],{"href":212,"rel":213},"https:\u002F\u002Fwww.emqx.com\u002Fzh\u002Fblog\u002Fmqtt-client-tools",[20],"MQTT client",[12,216,217,218,223],{},"具体使用方式请参阅 ",[16,219,222],{"href":220,"rel":221},"https:\u002F\u002Fgithub.com\u002Femqx\u002FNanoSDK\u002Fblob\u002F0.7.5\u002Fdocs\u002Fman\u002Flibnng.3.adoc#mqtt-message-handling",[20],"NanoSDK Doc","。",[24,225,226],{"id":226},"即将到来",[12,228,229],{},"规则引擎的消息重发布功能和规则热更新将在下一个版本中正式发布。同时会为 NanoMQ 增加 Reload 命令来进行配置文件热更新，为 MQTT over QUIC 桥接功能增加多次重连失败可以自动切换为标准 TCP 的功能（Fallback to TCP），来保证在不支持 QUIC 的网络下保持桥接连接功能正常。",{"title":83,"searchDepth":231,"depth":231,"links":232},2,[233,238,239,240,241],{"id":26,"depth":231,"text":26,"children":234},[235,237],{"id":52,"depth":236,"text":52},3,{"id":107,"depth":236,"text":108},{"id":120,"depth":231,"text":120},{"id":138,"depth":231,"text":138},{"id":153,"depth":231,"text":154},{"id":226,"depth":231,"text":226},"\u002Fimages\u002Fblog\u002Fzh\u002Fnanomq-newsletter-202209\u002Fcover.webp",400,700,"2022-10-08","9 月，NanoMQ 0.12.1 版本发布：桥接功能中增加了上下线事件和连接状态监控能力；重构升级了原有的日志系统；配置文件得到了简化。",false,"md",{},true,"\u002Fzh\u002Fblog\u002Fnanomq-newsletter-202209",{"title":6,"description":246},{"loc":251,"images":254,"lastmod":245},[255],{"loc":42},"zh\u002Fblog\u002Fnanomq-newsletter-202209",[258],"NanoMQ Newsletter","GyxfBeJZxmX9Lu7ssPpYZKact-OQ-2U5RvTawvnwnGI","\u002Fblog\u002Fnanomq-newsletter-202209",1794542897195]