[{"data":1,"prerenderedAt":293},["ShallowReactive",2],{"blog-post-zh-nanomq-newsletter-202205":3},{"post":4,"translationPath":292},{"id":5,"title":6,"author":7,"body":8,"cover":275,"coverHeight":276,"coverWidth":180,"date":277,"description":278,"draft":279,"extension":280,"meta":281,"navigation":282,"path":283,"pinned":279,"seo":284,"sitemap":285,"stem":288,"tags":289,"__hash__":291},"blog_zh\u002Fzh\u002Fblog\u002Fnanomq-newsletter-202205.md","NanoMQ Newsletter 2022-05｜v0.8.0 发布，新增 WebHook 拓展接口和连接认证 API",null,{"type":9,"value":10,"toc":263},"minimark",[11,23,30,37,45,50,53,62,73,76,80,83,89,92,98,101,162,170,173,182,185,189,192,195,198,204,212,216,219,244,247,254],[12,13,14,15,22],"p",{},"NanoMQ 是面向边缘计算的 ",[16,17,21],"a",{"href":18,"rel":19},"https:\u002F\u002Fwww.emqx.com\u002Fzh\u002Fblog\u002Fthe-easiest-guide-to-getting-started-with-mqtt",[20],"nofollow","MQTT"," 消息引擎+多协议消息总线。支持 MQTT 协议和 ZeroMQ 和 Nanomsg 等不同边缘常用总线协议，集成 broker 和 brokerless 消息模式，方便打造物联网边缘计算应用。",[12,24,25,26],{},"社区站地址：",[16,27,29],{"href":28},"\u002Fzh","https:\u002F\u002Fnanomq.io\u002Fzh",[12,31,32,33],{},"GitHub 仓库：",[16,34,35],{"href":35,"rel":36},"https:\u002F\u002Fgithub.com\u002Fnanomq\u002Fnanomq",[20],[12,38,39,40,44],{},"NanoMQ 项目一直保持着每月一个小版本+一个重要新功能的稳步迭代速度，v0.8.0 已于五月底正式发布（下载地址：",[16,41,42],{"href":42,"rel":43},"https:\u002F\u002Fgithub.com\u002Fnanomq\u002Fnanomq\u002Freleases\u002Ftag\u002F0.8.0",[20],"）。此次我们为大家带来了 2 个重要的功能更新：Event WebHook 以及可以与第三方 HTTP API 集成的连接认证接口。同时还新增了查看主题树结构的 HTTP API，各项性能优化和缺陷修复也在持续更新中。",[46,47,49],"h2",{"id":48},"高效易用的边缘-webhook-系统","高效易用的边缘 WebHook 系统",[12,51,52],{},"WebHook 是 EMQX 深受广大开源用户喜爱的一项功能，NanoMQ 也应社区呼声推出了相同的功能方便用户与第三方边缘计算应用集成。",[12,54,55,56,61],{},"NanoMQ 的 WebHook 系统与 EMQX 一脉相承，采用相同风格的配置方式。Webhook 的配置文件默认查找的路径为 \u002Fetc\u002Fnanomq_web_hook.conf，也可以通过命令行指定路径读取配置文件启动。具体配置项可查看 NanoMQ Docs ：",[16,57,60],{"href":58,"rel":59},"https:\u002F\u002Fnanomq.io\u002Fdocs\u002Fzh\u002Flatest\u002Fweb-hook.html#%E9%85%8D%E7%BD%AE%E9%A1%B9",[20],"https:\u002F\u002Fnanomq.io\u002Fdocs\u002Fzh\u002Flatest\u002Fweb-hook.html#配置项"," 。",[63,64,69],"pre",{"className":65,"code":67,"language":68},[66],"language-text","web.hook.enable=true\n## 格式示例\nweb.hook.rule.\u003CEvent>.\u003CNumber>=\u003CRule>\n","text",[70,71,67],"code",{"__ignoreMap":72},"",[12,74,75],{},"在设置中启用 WebHook 功能后，可以根据自己的需要配置触发规则，如需要将客户端上下线事件和所有匹配到 ”webhook\u002Fmsg\u002F#” 通配符主题的消息都转发到对应 HTTP API，则配置方式如下：",[77,78,79],"h3",{"id":79},"触发规则配置",[12,81,82],{},"在 etc\u002Fnanomq_web_hook.conf 可配置触发规则，其配置的格式如下：",[63,84,87],{"className":85,"code":86,"language":68},[66],"## 示例\nweb.hook.enable=true\nweb.hook.url=http:\u002F\u002F127.0.0.1:8888\nweb.hook.headers.content-type=application\u002Fjson\nweb.hook.body.encoding_of_payload_field=plain\nweb.hook.pool_size=32\nweb.hook.rule.client.connack.1={\"action\": \"on_client_connack\"}\nweb.hook.rule.client.disconnected.1={\"action\": \"on_client_disconnected\"}\nweb.hook.rule.message.publish.1={\"action\": \"on_message_publish\", \"topic\": \"webhook\u002Fmsg\u002F#\"}\n",[70,88,86],{"__ignoreMap":72},[12,90,91],{},"如此设置就能让 NanoMQ 自动捕获并吐出客户端上下线和消息发布的数据到对应的 HTTP API 了。目前 HTTP 请求的数据格式示例如下：",[63,93,96],{"className":94,"code":95,"language":68},[66],"## HTTP json格式示例\nConnack（客户端连接成功事件）:\n{\n  \"proto_ver\": 4,\n  \"keepalive\": 60,\n  \"conn_ack\": \"success\",\n  \"username\": \"undefined\",\n  \"clientid\": \"nanomq-6ecb0b61\",\n  \"action\": \"client_connack\"\n}\n\nPublish（消息发布）:\n{\n  \"ts\": 1650609267000,\n  \"topic\": \"webhook\u002Fmsg\u002F123\",\n  \"retain\": false,\n  \"qos\": 0,\n  \"action\": \"message_publish\",\n  \"from_username\": \"undefined\",\n  \"from_client_id\": \"nanomq-6ecb0b61\",\n  \"payload\": \"hello\"\n}\n\nDisconnect（客户端连接断开事件）:\n{\n  \"reason\": \"normal\",\n  \"username\": \"undefined\",\n  \"clientid\": \"nanomq-6ecb0b61\",\n  \"action\": \"client_disconnected\"\n}\n",[70,97,95],{"__ignoreMap":72},[12,99,100],{},"目前 NanoMQ 的 WebHook 系统支持以下事件：",[102,103,104,120],"table",{},[105,106,107],"thead",{},[108,109,110,114,117],"tr",{},[111,112,113],"th",{},"名称",[111,115,116],{},"说明",[111,118,119],{},"执行时机",[121,122,123,140,151],"tbody",{},[108,124,125,129,137],{},[126,127,128],"td",{},"client.connack",[126,130,131,136],{},[16,132,135],{"href":133,"rel":134},"https:\u002F\u002Fwww.emqx.com\u002Fzh\u002Fblog\u002Fmqtt-client-tools",[20],"MQTT 客户端","连接成功",[126,138,139],{},"服务端准备下发连接应答报文时",[108,141,142,145,148],{},[126,143,144],{},"client.disconnected",[126,146,147],{},"MQTT 客户端连接断开",[126,149,150],{},"客户端连接层在准备关闭时",[108,152,153,156,159],{},[126,154,155],{},"message.publish",[126,157,158],{},"MQTT 消息发布",[126,160,161],{},"服务端在发布（路由）消息前",[12,163,164,165,169],{},"如需要更多的消息事件请在 NanoMQ 项目的 ",[16,166,168],{"href":35,"rel":167},[20],"Github 页面","提交功能申请 Issue，我们会第一时间安排增加。",[12,171,172],{},"需要强调的是，NanoMQ 的 WebHook 功能是全异步操作，所有的匹配到的事件消息都会通过高效的内部 IPC 通道进入独立的专有线程进行处理，与 Broker 功能隔离，不会阻塞原有服务器里正常的消息流转，非常高效可靠。",[12,174,175],{},[176,177],"img",{"alt":178,"src":179,"width":180,"height":181},"NanoMQ WebHook","\u002Fimages\u002Fblog\u002Fzh\u002Fnanomq-newsletter-202205\u002F01.webp",1520,450,[12,183,184],{},"关于 WebHook 具体的配置信息和方式，以及如何调优请期待之后的 NanoMQ 系列教程文章。",[46,186,188],{"id":187},"http-连接认证-api","HTTP 连接认证 API",[12,190,191],{},"HTTP 连接认证是另一个常用到的集成功能，能够方便地与第三方认证服务器集成完成客户端的连接请求验证。另一个常用开源项目 Mosquitto 的同类型插件已经废弃不再维护，NanoMQ 的此项功能则填补了这一空白，而且也保持了和 EMQX 相同的功能和配置风格，方便用户上手。",[77,193,194],{"id":194},"认证规则配置",[12,196,197],{},"Authentication HTTP API 接口的配置文件读取方式与 NanoMQ 的其他配置文件相同。内部包含的配置项有：",[63,199,202],{"className":200,"code":201,"language":68},[66],"## 是否开启HTTP Auth 插件\n## Value: true | false\nauth.http.enable = true\n\n## Auth请求的目标HTTP URL\nauth.http.auth_req.url = http:\u002F\u002F127.0.0.1:80\u002Fmqtt\u002Fauth\n\n## HTTP Auth Request 请求方式\n## Value: post | get\nauth.http.auth_req.method = post\n\n## HTTP Request Headers for Auth Request\nauth.http.auth_req.headers.content_type = application\u002Fx-www-form-urlencoded\n\n## Parameters used to construct the request body or query string parameters\nauth.http.auth_req.params = clientid=%c,username=%u,password=%P\n",[70,203,201],{"__ignoreMap":72},[12,205,206,207,211],{},"配置完成后，NanoMQ 就会根据配置设置的请求格式将客户端 Connect 包的信息请求对应的 HTTP URL。并根据返回码判断是否允许客户端连接成功（Code 200 表示成功）。更详细的配置方式请参阅官网配置文档",[16,208,209],{"href":209,"rel":210},"https:\u002F\u002Fnanomq.io\u002Fdocs\u002Fen\u002Flatest\u002Fconfig-description\u002Fv014.html#parameter-description",[20],"。",[46,213,215],{"id":214},"其他功能优化及-bug-修复","其他功能优化及 Bug 修复",[12,217,218],{},"此外，NanoMQ 0.8.0 还有如下更新和优化：",[220,221,222,226,229,232,235,238,241],"ol",{},[223,224,225],"li",{},"更正客户端上下线时间消息中的时间戳 timestamp 字段为 UNIX 标准时间戳，之前为启动计时器。",[223,227,228],{},"修改了 NanoMQ 命令行工具的使用方式，去除了默认必须使用 “start\u002Fstop” 的限制。",[223,230,231],{},"增加 ZeroMQ 代理消息网关的文档。",[223,233,234],{},"修复了桥接连接被远端频繁关闭时导致的锁竞争问题。",[223,236,237],{},"修复了客户端大量发布消息导致积压时，Sub 客户端突然端口导致的数据竞争问题。",[223,239,240],{},"不再默认对遗愿消息内容进行 UTF-8 检查，只当客户端要求是才进行。",[223,242,243],{},"修复了一个使用 Retain As Published 消息时若消息属性为空会导致崩溃的故障。",[46,245,246],{"id":246},"即将到来",[12,248,249,250,61],{},"NanoMQ 将于下个月正式发布规则引擎，以及纳入新的数据库作为边缘数据全量持久化选项。目前此功能处于 Demo 阶段，在最新的主分支已可以使用。用户可以自行编译安装使用，欢迎尝鲜：",[16,251,252],{"href":252,"rel":253},"https:\u002F\u002Fgithub.com\u002Fnanomq\u002Fnanomq\u002F",[20],[12,255,256,257,262],{},"NanoSDK 将于下个月发布 MQTT over ",[16,258,261],{"href":259,"rel":260},"https:\u002F\u002Fwww.emqx.com\u002Fzh\u002Fblog\u002Fquic-protocol-the-features-use-cases-and-impact-for-iot-iov",[20],"QUIC"," 的 RC 版本，这是业界首个基于 C 语言的完整支持 MQTT 3.1.1 和 QUIC 功能的 MQTT SDK，敬请期待。",{"title":72,"searchDepth":264,"depth":264,"links":265},2,[266,270,273,274],{"id":48,"depth":264,"text":49,"children":267},[268],{"id":79,"depth":269,"text":79},3,{"id":187,"depth":264,"text":188,"children":271},[272],{"id":194,"depth":269,"text":194},{"id":214,"depth":264,"text":215},{"id":246,"depth":264,"text":246},"\u002Fimages\u002Fblog\u002Fzh\u002Fnanomq-newsletter-202205\u002Fcover.webp",684,"2022-06-06","NanoMQ v0.8.0 已于五月底正式发布，该版本带来了 2 个重要的功能更新：Event WebHook 以及可以与第三方 HTTP API 集成的连接认证接口。",false,"md",{},true,"\u002Fzh\u002Fblog\u002Fnanomq-newsletter-202205",{"title":6,"description":278},{"loc":283,"images":286,"lastmod":277},[287],{"loc":179},"zh\u002Fblog\u002Fnanomq-newsletter-202205",[290],"NanoMQ Newsletter","6PxaEUZEE8rhA1sEseGBIVu1psqDBF48ecFbH6RXrWU","\u002Fblog\u002Fnanomq-newsletter-202205",1794542897589]