-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Bug with loki-stack chart while adding datasource #3149
Comments
I just got the same issue, the endpoint returns a parser error while we can still send query to the data source. |
looks like loki-stack is not being maintained properly. |
loki-stack is deprecated |
@Sheikh-Abubaker Is there any successor to loki-stack? If not, does anyone know a good and helm driven way to add loki to my kube-prometheus-stack? |
@EHJ-52n try using loki |
but then the Chart should be updated with |
Will there be migration documentation to move from loki-stack? |
loki-stack is deprecated, is this news from grafana official? |
The official Loki documentation still references the loki-stack Helm chart for installing monolithic Loki on Kubernetes: https://grafana.com/docs/loki/latest/setup/install/helm/install-monolithic/ This should be changed. |
Uh... that took forever to debug before reading this. This line is still to be fixed ASAP.
|
i got the same issue. |
I faced the same error. It is due to the loki-stack helm chart is not updated with the correct image version. As mentioned here #3507 , update the container image version to 2.9.3 in the statefulset object and it will be good to go. Please update the helm chart with correct app version accordingly. |
Hi,
I am creating this issue to let you know that with recent version, I tried adding datasource in separate grafana as http://loki:3100 and try to save and test but it fails with error "Unable to connect with Loki. Please check the server logs for more details." but I am able to see logs in dashboard. This is happening in GKE and kind cluster both as testing environment.
Please take a look as so many can get confused with this.
Getting below error in grafana pods
"logger=tsdb.loki endpoint=checkHealth pluginId=loki dsName=loki dsUID=cdn1r5hikan7kc uname=admin fromAlert=false t=2024-05-30T11:24:42.682252191Z level=info msg="Prepared request to Loki" duration=23.256µs queriesLength=1 stage=prepareRequest runInParallel=false
logger=tsdb.loki endpoint=checkHealth pluginId=loki dsName=loki dsUID=cdn1r5hikan7kc uname=admin fromAlert=false t=2024-05-30T11:24:42.861757897Z level=error msg="Error received from Loki" duration=179.38691ms stage=databaseRequest statusCode=400 contentLength=65 start=1970-01-01T00:00:01Z end=1970-01-01T00:00:04Z step=1s query=vector(1)+vector(1) queryType=instant direction=backward maxLines=0 supportingQueryType=none lokiHost=loki.monitoring.svc.cluster.local:3100 lokiPath=/loki/api/v1/query status=error error="parse error at line 1, col 1: syntax error: unexpected IDENTIFIER" statusSource=downstream
logger=tsdb.loki endpoint=CheckHealth t=2024-05-30T11:24:42.861870966Z level=error msg="Loki health check failed" error="error from loki: parse error at line 1, col 1: syntax error: unexpected IDENTIFIER"
logger=context userId=1 orgId=1 uname=admin t=2024-05-30T11:24:42.861963433Z level=info msg="Request Completed" method=GET path=/api/datasources/uid/cdn1r5hikan7kc/health status=400 remote_addr=127.0.0.1 time_ms=181 duration=181.02212ms size=106 referer=http://localhost:3001/connections/datasources/edit/cdn1r5hikan7kc handler=/api/datasources/uid/:uid/health status_source=server"
The text was updated successfully, but these errors were encountered: