2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Hi,
Can you update your question to detail a bit what kind of services you're trying to monitor with this Grafana ? "no healthy upstream" is often related to the systems being monitored by Grafana.
Best,
Didier
0
Have you reviewed this article https://repost.aws/knowledge-center/grafana-504-timeout-vpc to see if it resolves your issue?
This article doesn't resolve my issue. I cannot open my workspace web page: https://g-******.grafana-workspace.ap-northeast-1.amazonaws.com/. I only get 503 no healthy upstream when accessing my workspace.
Contenus pertinents
- Réponse acceptéedemandé il y a un an
- demandé il y a un an
- demandé il y a 2 mois
- demandé il y a 10 mois
AWS OFFICIELA mis à jour il y a un an- AWS OFFICIELA mis à jour il y a 2 ans
I have two datasources: postgresql and prometheus. However, I cannot open this workspace url with my browser, and this should not be related to my data sources. If my data sources have any problems, I should be able to log in the grafana website and see broken dashboards. However, when I open the workspace url, only 503 error is returned, and there is no login page anymore. I found this issue yesterday, and I didn't do anything with my aws account yesterday.