Fix uid for tempo datasource

[bisgaard-itis]

What do these changes do?

Hardcode the uid of the Tempo datasource. This seems to be the issue in #1156. I can see that other datasources which are referenced in dashboards have hardcoded uids. Once this is merged I will have to check that the rpc sections of the simcore service dashboards all work as expected.

Related issue/s

• fixes Grafana: services dashboards has misconfigured RPC metrics in master and staging #1156

Related PR/s

Checklist

• I tested and it works

[YuryHrytsuk]

Let me test it on AWS Master before merging.

[bisgaard-itis]

Let me test it on AWS Master before merging.

That would be great! Thanks a lot. Let me know when you have given it a try

[YuryHrytsuk]

Let me test it on AWS Master before merging.

That would be great! Thanks a lot. Let me know when you have given it a try

The panels seems to have no errors now. But they show no data

[YuryHrytsuk]

Let me test it on AWS Master before merging.

That would be great! Thanks a lot. Let me know when you have given it a try

The panels seems to have no errors now. But they show no data

@bisgaard-itis you can check it on your own on aws master (you change is deployed there manually)

[YuryHrytsuk]

This might be related to the fact that on aws master we use aws rabbit (not self-hosted)?

[bisgaard-itis]

Let me test it on AWS Master before merging.

That would be great! Thanks a lot. Let me know when you have given it a try

The panels seems to have no errors now. But they show no data

@bisgaard-itis you can check it on your own on aws master (you change is deployed there manually)

@YuryHrytsuk this is just because there is no data. Maybe noone was hitting these endpoints within the given time frame. I just checked again on aws master and it looks fine to me when I look at the catalog for the last 3 hours:

[YuryHrytsuk]

Cool! Thanks 🙏