Loki Trigger Server Address doesn't support sub path #7639
Replies: 2 comments
-
|
we can update the path as |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Continues via #7648 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
KEDA uses an community integration for LOKI based scaling: https://keda.sh/docs/2.19/scalers/loki/
Internally it tries to use these api endpoints to make query: https://grafana.com/docs/loki/latest/reference/loki-http-api/
But there is another issue inside the
loki_scalercommunity code: https://github.com/kedacore/keda/blob/main/pkg/scalers/loki_scaler.go#L122here, it overrides the existing url path with
/loki/api/v1/querydue to which the final url becomeshttp://<loki-host>:3100/loki/api/v1/query.it only accepts
serverAddresswhich has a base url likehttp://<loki-host>:3100, and not any url with sub-path.If there is a extra sub path to the url,
for eg:
http://<company-host>:3100/<product_name>/grafana,instead of the url becoming
http://<company-host>:3100/<product_name>/grafana/loki/api/v1/query,it becomes
http://<company-host>:3100/loki/api/v1/query, which is not correct in our case.Need help with a workaround.
Beta Was this translation helpful? Give feedback.
All reactions