You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When receiving messages locally via MQTT and processing or enhancing them it would be great if we could lookup the timestamp when the publisher created the message in the user properties of the message instead of having to parse the complete message.
In other Transports like RabbitMQ and DAPR the Timestamp is set.
Describe the solution you'd like
Set the Property "Timestamp" in MQTT user properties (either when EnableRoutingInfo is set, or always).
Currently the timestamp is set on the IEvent, but ignored when using MQTT as transport. See:
Is your feature request related to a problem? Please describe.
When receiving messages locally via MQTT and processing or enhancing them it would be great if we could lookup the timestamp when the publisher created the message in the user properties of the message instead of having to parse the complete message.
In other Transports like RabbitMQ and DAPR the Timestamp is set.
Describe the solution you'd like
Set the Property "Timestamp" in MQTT user properties (either when EnableRoutingInfo is set, or always).
Currently the timestamp is set on the
IEvent
, but ignored when using MQTT as transport. See:https://github.com/microsoft/project-furly/blob/01480644d1b985c49b6b820db6179ef316ad79cd/src/Furly.Extensions.Mqtt/src/Clients/MqttMessage.cs#L125-L129
Describe alternatives you've considered
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: