feat: send diode data over MQTT #222
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces support for a new telemetry MQTT topic in the fleet configuration manager and related agent components. The main changes ensure that when running with the fleet config manager, the agent automatically configures the OTLP gRPC URL and handles the new telemetry topic throughout the configuration, bridge server, and tests. The update improves observability and integration with telemetry pipelines.
Fleet configuration and topic management:
telemetryMQTT topic across configuration, topic templates, and token response structures, ensuring it is generated and available alongside existing topics. [1] [2] [3]Agent startup and OTLP configuration:
localhost:4317when the fleet config manager is active, ensuring consistent backend configuration.Bridge server enhancements:
BridgeServerto store and manage the telemetry topic, with new setter and getter methods for thread-safe access. [1] [2]Testing improvements: