Menu

#414 Unit of Measure for Ranges in a LimitAlertCondition

Revision
accepted
David
4 days ago
2026-05-07
No

This ticket is created based on APKP discussions (https://github.com/ornet-ev/apkp/issues/36):

Do we need such a requirement to provide more information about the Units of Measure for Ranges in a LimitAlertCondition?

To assure that the unit of the limits in pm:Range is the unit of the referenced pm:AlertConditionDescriptor/pm:Source, an SDC ALERT PROVIDER shall assure that the following is true:

If there is no pm:Source that is a Metric with a UOM, there is no pm:Range in the pm:AlertConditionDescriptor or pm:AlertConditionState
There is only one pm:Source with a UOM or multiple pm:Source with the same UOM for a pm:AlertConditionDescriptor or pm:AlertConditionState that contains a pm:Range.
Similarly for an operation:

If there is no @OperationTarget that is an pm:AlertConditionDescriptor where the UOM can be derived from the pm:Source, there is no pm:Range in the pm:SetValueOperationState

Discussion

  • David

    David - 4 days ago
    • labels: --> breaking PROVIDER backward compatibility
    • status: unread --> accepted
    • assigned_to: David
     
  • David

    David - 4 days ago

    2026-05-11: Agreed. Unit of measures should be added to limit alert condition. Make this property mandatory even if the source is a metric wih given unit of measure.

     
  • David

    David - 4 days ago
    • Milestone: untriaged --> Revision
     
  • David

    David - 4 days ago

    2026-05-11: Agreed. Unit of measures should be added to limit alert condition.

     

Log in to post a comment.

MongoDB Logo MongoDB