How could we get the acknowledgement of data sent using thin-edge to Events, Alarm and measurements?

Forum
1

What product/components do you use and which version/fix level are you on?

latest

Is your question related to the free trial, or to a production (customer) instance?

production

What are you trying to achieve? Please describe it in detail.

How could we get the acknowledgement of data sent using thin-edge to Events, Alarm and measurements?

Do you get any error messages? Please provide a full error message screenshot and log file.

Have you installed all the latest fixes for the products and systems you are using?

yes

2

How do you send the data? Are you using the cli for that or using another library to send data to the local broker?

  • cli: There is a --qos command which you could set to 2.

  • Other library: The topics are bridged via qos 2, such that as soon as you made sure the payload was send to the local broker (e.g. via sending with qos 2) the data will be send to cumulocity with qos 2 as well.

3

QOS is quality standard and it is the contract between Edge and Cloud

Message failures can also occur once after the message is reached to the cloud.

In this scenario our custom code in edge persists all failures and and should retry until message is successfully stored in cloud

Therefore against each published telemetry (D2C) message,there must be acknowldgement(C2D) to ensure the cloud has accepted message without any systeam or cloud component crash internally

And Assuring QoS implementation does not always gurantee Successful delivery of messages

4

There is no such thing on the MQTT implementation.
If you need that, you could use the RestAPI which would give you back a 201.

5

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.