Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set Timestamp in UserProperties of message when using MQTT Transport #2277

Closed
quality-leftovers opened this issue Jul 2, 2024 · 3 comments
Closed
Labels
feature request New feature or request
Milestone

Comments

@quality-leftovers
Copy link
Contributor

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

  • Having a microservice consume all messages, add the timestamp and re-publish them to another topic
  • Using DAPRD as middleware since it adds the Timestamp property. But DAPR trasnsport is already used to send the data to azure cloud

Additional context
Add any other context or screenshots about the feature request here.

@marcschier marcschier added the feature request New feature or request label Jul 2, 2024
@marcschier marcschier added this to the 2.9.10 milestone Jul 2, 2024
@marcschier
Copy link
Collaborator

Easy to add, will do it in next release.

@marcschier
Copy link
Collaborator

Added "TineStamp" property, but it is only supported with Mqtt v5

@quality-leftovers
Copy link
Contributor Author

quality-leftovers commented Jul 3, 2024

Thanks.

That happend faster than I could blink ;).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants