CASE WITH 2 DATA POINTS

See incidents_2dp.jsonand alerts_2dp.json

When the alerts query is returning 2 datapoints, T1 and T2:

ACTUAL: T2 is rendered as start date, no bar is rendered.

EXPECTED: T1 is start date, T2 is end date, bar is rendered

CASE WITH 3 DATA POINTS

See incidents_3dp.jsonand alerts_3dp.json

When the alerts query is returning 3 datapoints, T1 and T2 and T3:

ACTUAL: T1 is start date, T2 is end date, bar is rendered

EXPECTED: T1 is start date, T3 is end date, bar is rendered

The wrong end date is also breaking the resolved/firing state of the alert

avoznese@redhat.com reproduce the bug with oc apply -f alert2.yaml. Install cluster health analyzer first of course (pull the latest main)