Searching for an explanation to an alarm in Cumulocity

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

Cumulocity IoT ( Version 1013.0.260)

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

It is related to a customer instance which we are using with partners in the Software AG Research department.

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

I was wondering if somebody could explain this alarm to me:

The confusing part of the Alarm is the “ood”, because I have no clue what it stands for. If someone could explain me what this means I would be very grateful.

I stumbled upon this alarm when I was searching for a reason why some off our measurements were not offloaded to DataHub. This is not the only value for which I got the Alarm but they all have the same structure. The values for the described series “AxisBCurrent” of type “c8y_Current” are gathered via OPC UA and should be created as measurements with the help of the device protocols for OPC UA Cumulocity provides (in this case called “IGH-Validierungsplattform” using the data from the “PT16-PTW” OPC UA server).

Kind Regards,
Fabian Lehr

Out of date?

What would out of date mean in that context? That there is no value for a date or that the value for date is considered to old by Cumulocity or the OPC UA Server?
Since there are no measurements created due to this error I cant check the data of the measurements. But before I contact our project partners to have them look over the OPC UA Servers I want to be sure that its not an issue with Cumulocity. So are there any known scenarios that cause an error like this?

I did a quick search, and it does not look like any Cumulocity component is producing such an alarm. Do you have a smart rule, EPL rule or Analytics Builder model on this tenant that might be producing this?

@Harald_Meyer no we aren’t using any of the mentioned components. The only Cumulocity component we are using except DataHub are the device protocols for OPC UA as I mentioned above. If you are sure that the error isn’t produced in Cumulocity I will ask our project partners to have a look on the issue.
Thank you for your fast reply.

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