fix(backend): tempo cloud connection string

[xoscar]

This PR fixes a confusing way of dealing with the tempo cloud http connection, as pasting the given endpoint from the webapp uses :443 instead of https

Changes

• Defaults :443 port to https

Fixes

• [bug] Polling for traces from Grafana Cloud Tempo does not work #3507

Checklist

• tested locally
• added new dependencies
• updated the docs
• added a test

[xoscar]

With a url like this:

tempo-us-central1.grafana.net:443

The parsing method returns

http://tempo-us-central1.grafana.net:443

Which breaks the getTraceById logic.

[xoscar]

443 and 1 (using https://tempo-us-central1.grafana.net) should be also valid ports

[schoren]

I've never seen port 1 being used. Is there any docs about this port?

[xoscar]

For some reason the url parser uses 1 as port when using something like https://tempo-us-central1.grafana.net/

[xoscar]

[schoren]

That looks like a bug in the URL parsing library. Do you know why we're using an URL parser other than the go's stdlib one?

[xoscar]

Yeah the standard makes it worse in some cases, here's a table

[schoren]

I see. That makes sense. What I would do is handle the case of port "1" and replace it by a correct default port, for example:

if port == 1 {
  if schema == "http" {
    port = 80
  }
  if schema == "https" {
    port = 43
  }
}

[adnanrahic]

This is awesome. When will this be ready for me to try it?