Hi,
The parameter heatline on the Alarm Console depicts the last 24 hour alarm state of a parameter.
This means that for a column parameter, all the indexes in the same element generating an alarm to that particular element are accounted for?
Or are we considering a heatline for the table row key that generates the alarm?
Thanks,
Hi Bruno,
The parameter heatlines for table parameters are per table row. You can see the same heatlines in the element card on the reports pages as well. There you can clearly see how it expands to the row level (you need to check '[x] Expanded view':
ok Bruno, we can add a small annotation there for table parameters.
Thx for the question & feedback!
Hi Bruno,
I believe your best bet is to document your use-case in the new feature suggestion section.
Hi Ive,
Thanks, but I’m actually trying to understand first how we are doing this. If it’s indeed bound to the parameter itself (I’m just assuming after reading Help), why are the statechanges / timetrace tables (the sources for the heatline data) indexed (partitioning keys) with the Table Primary Keys?
Hi Bruno,
My apologies, I misunderstood the question.
I can confirm the timeline is tied to the parameter in the cube.
I’m not sure how the processing happens in the background, hopefully, someone else can shed some light on this.
Hi Pieter,
Thanks, that makes sense. But in that case we need to improve our documentation, as this is not crystal clear reading help:
Heatlines > Parameter heatline
This column displays a heatline depicting the parameter alarm state over the last 24 hours.
Only displayed on systems using a Cassandra database.