chore: update changelog entries
This commit is contained in:
parent
11dbef3ec0
commit
00301935bb
|
@ -1 +1 @@
|
|||
For helm charts, add MQTT ingress bridge; and removed stale `mgmt` references.
|
||||
Add MQTT ingress to helm charts and update helm charts documentation
|
||||
|
|
|
@ -1 +1 @@
|
|||
In dashboard API for `/monitor(_current)/nodes/:node` return `404` instead of `400` if node does not exist.
|
||||
Ensure Monitor API `/monitor(_current)/nodes/:node` returns `404` instead of `400` if node does not exist.
|
||||
|
|
|
@ -1 +1 @@
|
|||
如果 API 查询的节点不存在,将会返回 404 而不再是 400。
|
||||
如果 API 查询的节点不存在,将会返回 `404` 而不再是 `400`。
|
||||
|
|
|
@ -1 +1 @@
|
|||
Fix: configuration parameter `mqtt.max_awaiting_rel` had no effect.
|
||||
The configuration parameter `mqtt.max_awaiting_rel` was not functional and has now been corrected.
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
For operations on `bridges API` if `bridge-id` is unknown we now return `404`
|
||||
For operations on Bridges API if `bridge-id` is unknown we now return `404`
|
||||
instead of `400`. Also a bug was fixed that caused a crash if that was a node
|
||||
operation. Additionally we now also check if the given bridge is enabled when
|
||||
doing the cluster operation `start` . Affected endpoints:
|
||||
|
|
|
@ -0,0 +1 @@
|
|||
将数据桥接和连接器的 resume_interval 参数值设为 health_check_interval 和 request_timeout / 3 中的较小值,以解决请求超时的问题。
|
|
@ -0,0 +1 @@
|
|||
当调用 `/nodes/:node[/metrics|/stats]` API ,若节点不存在则返回 `404` 状态码。
|
|
@ -0,0 +1 @@
|
|||
修复了当删除一个使用中的 ingress 类型的桥接时,未提示存在规则依赖的问题。
|
|
@ -0,0 +1 @@
|
|||
修复 `/monitor_current` API ,使其仅查看当前 节点。修复了 `/stats` API,以防止当集群中的一个或多个节点关闭时出现崩溃。
|
|
@ -0,0 +1 @@
|
|||
在收到不可恢复的错误时,不要增加 'actions.failed.unknown' 规则指标计数。
|
|
@ -1,2 +1,2 @@
|
|||
Implemented Kafka Consumer bridge.
|
||||
Implement Kafka Consumer bridge.
|
||||
Now it's possible to consume messages from Kafka and publish them to MQTT topics.
|
||||
|
|
|
@ -1,4 +1,4 @@
|
|||
In this pull request, we have enhanced the error logs related to InfluxDB connectivity health checks.
|
||||
Enhance the error logs related to InfluxDB connectivity health checks.
|
||||
Previously, if InfluxDB failed to pass the health checks using the specified parameters, the only message provided was "timed out waiting for it to become healthy".
|
||||
With the updated implementation, the error message will be displayed in both the logs and the dashboard, enabling easier identification and resolution of the issue.
|
||||
|
||||
|
|
Loading…
Reference in New Issue