Hello Dojo,
When enabling Absolute baseline alarming on a partial table, the behavior does not seem to work correctly. So far I have noticed that the current value is not being filled in and is showing not initialized, other times only a small amount of the rows are shown.
When I remove the partial option from the table, the baseline details table fills in correctly.
Does baseline need additional settings to work with partial tables?
Below are pictures showing the baseline table and the table that is being alarmed (Expected RX Bitrate is the alarmed column).
For everyone’s clarity, as Data-Core member, I confirm Miguel's assessment.
The described issue is being addressed under the internal task DCP253128, which is currently in the backlog of our Cube Team in a "to be scheduled" state. This means that we don't yet have a target release date for the fix.
Hi Luis,
Would you be able to clarify what you mean when saying the issue will be adressed?
Is baseline feature going to be supported for partial tables?
Or is Cube (alarm template editor) going to be adapted so it's clear that base line feature can not be used on partial tables?
Hi Simon, You can find more details in the task.
For transparency, the conclusion is that the baseline feature is currently not supported on partial tables. We will update dataminer docs accordingly.
Hi Gabriel,
It seems expected behavior.
See DCP253128.