Hi,
the documentation
is vague here: Would this rule also apply if an alarm already exists (and thus just the counter increased)? Or would I have to clear the alarm first?
Best regards,
Harald
Hi,
the documentation
is vague here: Would this rule also apply if an alarm already exists (and thus just the counter increased)? Or would I have to clear the alarm first?
Best regards,
Harald
It says when an alarm is created, so updating counters (existing alarm) won’t have any effect.
Thank you, I also confirmed the same through a test. Though I do not think that is entirely obvious. The REST API you call is still a POST, which indicates “new” and you have to be aware that the deduplication feature of Cumulocity applies.
I created a ticket to make this clearer on the documentation.
Verify that the alarm was created and not duplicated from somewhere.
This text should be changed in my opinion. Whatever “duplicated from somewhere” means
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.