-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
loki ingress endpoint doesn't work #202
Comments
I can confirm this is the case. It seems like the webroot isn't properly set as removing the relation between loki and traefik and refreshing the source turns it green. Adding it back again and refreshing the datasources, however, it continues to work, so this might very well be connected to canonical/traefik-k8s-operator#78, as that usually manifests by deploying it as a bundle. |
When I deploy the bundle this does not happen for me. Can anyone confirm that this bug still exists? |
|
I can't reproduce it either, so seems like the fixes to traefik solved it. |
Bug Description
After deploying the COS Lite bundle (https://github.com/canonical/cos-lite-bundle), the Grafana dashboard datasources section looks like this:
The Alertmanager and Prometheus datasources successfully pass the Grafana checks but the Loki one fails due to receiving a 404 error.
To Reproduce
Environment
juju status
snap list
Relevant log output
`juju debug-log --replay`: https://termbin.com/wndl
Additional context
No response
The text was updated successfully, but these errors were encountered: