You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would involve adding ingress relations to mimir, tempo, as they are currently missing from the terraform module.
This may be a bit involved: after manually relating mimir to traefik, I am getting a 404 from nginx for all mimir endpoints.
This could have been happening because the /status path is already used by an nginx endpoint mapping.
We shouldn't shadow known workload paths with our custom ones.
The trouble is that /status may be a hard dep for the nginx exporter.
Why do we want to have tempo? It has no UI. Mimir potentially makes sense, but I'd honestly skip it. I'm sure I've asked for this at some point, but I think we can skip this.
We need to have mimir, tempo listed on the catalogue page.
Depends on:
catalogue
relation cos-lib#113This would involve adding ingress relations to mimir, tempo, as they are currently missing from the terraform module.
This may be a bit involved: after manually relating mimir to traefik, I am getting a 404 from nginx for all mimir endpoints.
References:
catalogue
+ingress
tempo integrations in COS TF module #253The text was updated successfully, but these errors were encountered: