v1.6.0

Significant Changes

• Enable multiple applications to connect to uplink over bridge

NOTE: Please ensure that you only accept an action and send responses from one of the connected apps, this is the expected behavior for apps connecting to uplink over TCP.

• Rework config for serializer_metrics:

[serializer_metrics]
- buf_size = 10
- flush_period = 30
+ enabled = true

• Publishes serializer_metrics as JSON to the topic "/tenants/{tenant_id}/devices/{device_id}/serializer_metrics/jsonarray" by default. Can be reconfigured by setting the optional topic field in the config.toml file.
• Adds stream_metrics to keep track of data streams as they flow through uplink. This feature can be enabled by adding the following to config.toml:

[stream_metrics]
enabled = true

What's Changed

• fix: code improvements and clippy suggestions by @de-sh in #77
• fix: use action_id and let it alias as id for "action_status" by @de-sh in #78
• feat: Add ignore_actions_if_no_clients by @bmcpt in #79
• fix: default to no persistence by @de-sh in #81
• feat: make keep_alive configurable by @de-sh in #80
• feat: let Serializer query Packages batch size by @de-sh in #83
• feat: stream name from Package in Serializer by @de-sh in #84
• feat: collect and log batching_latency as a metric by @de-sh in #86
• fix: serializer metrics ouroboros by @de-sh in #85
• feat: collect and forward stream_metrics by @de-sh in #87
• fix: compiling to non linux/android targets by @de-sh in #88
• feat: multiple tcp collectors, broadcast actions by @de-sh in #76
• feat: compile binary for m1 mac on release by @de-sh in #89

Full Changelog: v1.5.1...v1.6.0