-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Full LogQL not yet supported? #985
Comments
The newest loql capabilities are still experimental and are won't be available in Grafana until 6.4 We hope to have logcli updated soon as soon as we finish some API details Please note, the current API is going to change! |
OK, will wait for |
I am experiencing the same issue on Grafana 6.4.2 and Loki from docker hub What is the current status of this issue? Should it be working? |
No this is not available yet in Grafana, @davkal do we have an issue on Grafana side ? Also I notice the path Grafana is using currently is wrong it should be https://github.com/grafana/loki/blob/master/docs/api.md#get-lokiapiv1query_range If you still want to use this you can @Horkyze , you can use Loki as a Prometheus datasource, although you won't have label and label value completion it will still works in dashboard and explore. When adding Loki as a Prometheus datasource use this URL path: here is some example Using ExploreUsing a dashboardBasically Loki is 100% compatible with the Prometheus API for those queries :) |
Thanks for quick reply. Could you provide you datasource config please?
|
I'm guessing you're on Loki 0.3, you need at least this commit 364b5bc which will be in the soon to be released 0.4 |
Thanks, it is working now :) However with some small issue (which I resolved) grafana/grafana#19764 |
The grafana team is working on this for 6.5. Sorry for the delay. |
This doesn't seem to work in 6.5, am I correct? Can we maybe reopen this issue, if that is the case? |
It should work. |
Ho ! Does explore works ? It seems you’re using a graph panel, this works
only with Prometheus data source but Loki can be one if you add /loki at
the end of the data source path.
Le lun. 20 janv. 2020 à 07:50, Chris Werner Rau <notifications@github.com>
a écrit :
… I'm using Grafana 6.5.3 and Loki 1.2.0.
When I try to query Loki, I get the following error message: legacy
endpoints only support streams result type, current type is matrix
[image: image]
<https://user-images.githubusercontent.com/14326070/72727613-a9979d00-3b8b-11ea-84ed-c7f5d5a3a399.png>
Maybe I'm doing something wrong?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#985?email_source=notifications&email_token=AAIBF3PBKLV6UXA3NFXJN7LQ6WM2TA5CNFSM4IU2H64KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJMQTVY#issuecomment-576260567>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIBF3N73CQFEUMBGTSI3Z3Q6WM2TANCNFSM4IU2H64A>
.
|
@ivanahuckova which Grafana version has native metrics support for Loki ? @cwrau the thread above explain how to use loki as a prometheus data source in the meantime. |
I just tried 6.6.0-beta1 for #20300, and this works as well. The only thing that's missing is the legend format that's available for Prometheus and alerting 😞 So even in 6.6.0-beta1 I'll need Loki as a Prometheus datasource, at least for alerting |
Yeah for alerting it will take time also, we use Loki as prom data source internally and it does the job. |
I've just installed from scratch on a new cluster using Helm. The missing legend format is a major issue and makes it Loki as a dashboard graphing tool useless to me, unless I have one series per panel, turn off legends and tooltips and use a sensible panel name. The default metric names are 300+ characters long, eg:
|
The latest Grafana support this now. |
If I'm looking at
https://github.com/grafana/loki/blob/master/docs/querying.md#range-vector-aggregation
, it seems that there's already an option for queried of the formcount_over_time({level="ERROR"}[5m])
to be evaluated properly.However, I'm running Grafana
6.3.2
and I keep getting this message:If I'm not mistaken, this is because the option for range vector aggregation was only added to
master
5 days ago (in #654), and the latest version is6.3.5
that was release 7 days ago, right?Or is there capability to do the above query in
6.3.5
already?The text was updated successfully, but these errors were encountered: