[Uptime] Redirects in UI

[andrewvc]

This is the non-design issue tracking

With elastic/beats#14125 we will now include a list of redirects traversed in checking a URL. There's currently no way to see this info. A check that involves redirects may be interpreted differently than one that does not, so we should indicate this. One key difference is that redirects can be slower than a non-redirects, so one may interpret latency differently.

See #99 for the design of this feature

[katrin-freihofner]

Monitor page status

Adding information about redirects: Heartbeat followed N redirects while executing ping.

Individual check details

Adding list of redirected Urls and sort down icon

[shahzad31]

@katrin-freihofner are we displaying redirects in expanded row in history panel on details page or on monitor list?

From image

it looks like it's a expanded row in monitor list also figma link images says the same https://www.figma.com/file/lDlGXMzUTnzAlHPQu7lZAH/Uptime?node-id=130%3A1

but andrew comments and expanded row body in above image seems like it's history panel, since it also has Reponse Body.

Are we going to display in both places?

[katrin-freihofner]

@shahzad31 I think the redirect info belongs to the details page. cc @andrewvc

[andrewvc]

Yes, the mock is for the history panel in the details page. Not sure where the confusing comments are, but I'm on the same page as @katrin-freihofner

[shahzad31]

Confusion was from the image actually, row style is from monitor list

Katrin clarified it.

[shahzad31]

I think for the monitor detail, i liked the original idea better

just displaying text doesn't convery much, we should also display popover with redirect list

In original issue, i think it was recommended that we update the text but we should keep the popover panel.

WDYT? cc @andrewvc @katrin-freihofner

[katrin-freihofner]

The header gives only a quick overview. The details about redirects are further down in the table. That is why we decided to go that way.