[Synthetics] Waterfall level changes for incomplete requests

[paulb-elastic]

⚠️ needs more refinement

With https://github.com/elastic/synthetics/issues/737, we will get data for more incomplete requests. Once this is available, we may want to consider making it clear in the waterfall chart (maybe with a different colour / key to identify it as incomplete).

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[paulb-elastic]

@drewpost my suggestion is that we show the timings / bars for the data we have available. For instance, maybe we only actually have separate timings for DNS, connect and TLS, and then for everything else (i.e. where we don't have a breakdown of the timing we can attribute to another specific part of the request). For this, we could have a category such as incomplete which is used in the legend and chart with a specific colour (maybe a grey of some type)?

WDYT? Will this need any design input?

@vigneshshanmugam does that seem reasonable based on the data we're not collecting for these cases?

[paulb-elastic]

Need to discuss further - added to Tech Sync agenda (and moved out of in progress)

[paulb-elastic]

At the moment we have the standard network level timings:

So for example get a request something like:

For an incomplete request (where we don't know the breakdown after the TCP connection for example), we might want to greyed out timing breakdown, something like this:

[paulb-elastic]

@shahzad31 I was discussing with @drewpost and he was wondering if there's a non colour fill option that we could use here, such as stripes / dots, or something else? I looked on a normal lens visualisation but couldn't see anything, but not sure I'll be able to see all the capabilities like this.