Preview of Explore Logs, a new way to browse your logs without writing LogQL
1–10 of 95 posts
Re: Preview of Explore Logs, a new way to browse your logs without writing LogQL
#2Why have explore logs as a separate app instead of bundled with Loki? It would be nice if Loki had the same kind of barebones querying/debugging functionality as Prometheus...
Re: Preview of Explore Logs, a new way to browse your logs without writing LogQL
#3I recently setup Victoria Metrics + https://github.com/prometheus/snmp_exporter + Grafana to get start tracking bandwidth on my top of rack switches in my Datacenter rack which has been a pretty awesome setup. The way you can auto generate a config for your SNMP MIBs with SNMP Exporter was unexpectedly not a terrible experience.
My next task is to get centralized logging going with Victoria Logs + Vector, I'll have to check this out once I get everything setup. I believe I can use LogQL with Victoria Logs but I haven't tried it out yet. https://docs.victoriametrics.com/victorialogs/logsql/
Re: Preview of Explore Logs, a new way to browse your logs without writing LogQL
#4[deleted]
Re: Preview of Explore Logs, a new way to browse your logs without writing LogQL
#5I thought it was a standalone web app, but it's integrated into Grafana. I'm confused a bit. There's already Explore functionality in Grafana for Loki. Seems like spreading the efforts for no reason.
Re: Preview of Explore Logs, a new way to browse your logs without writing LogQL
#6I'm not really a cloud expert so maybe I'm fundamentally missing something about how I'm "supposed to work", but honestly all I have ever wanted to do, when looking at logs, is see the log from one process, from beginning to end, as a text file. You can of course do this using kubectl but only for the most recent two instances of a given pod which isn't helpful when investigating an incident that happened a while ago.
It seems nobody else cares about this use case and wants you to use LogQL and the incredibly clunky Grafana web UI instead, because it makes it possible to aggregate across many different processes, slice and dice by various labels, etc., which as I said, I have never (or almost never) actually wanted to do.
Hopefully this new UI is a step in the right direction as people won't need to futz around with LogQL anymore, but it seems like it still doesn't quite do what I want.
Re: Preview of Explore Logs, a new way to browse your logs without writing LogQL
#7While this is a step in the right direction, just let me write something closer to SQL. Influx did this correctly.
Re: Preview of Explore Logs, a new way to browse your logs without writing LogQL
#8While this is a step in the right direction, just let me write something closer to SQL. Influx did this correctly.
[deleted]
Re: Preview of Explore Logs, a new way to browse your logs without writing LogQL
#9I'll preface this with the fact I haven't look at Loki in a bit, so maybe this has changed. But I found the documentation needing a lot of work and the configuration for promtail to be obtuse and not very user friendly. I haven't used it for those reasons, not because of the query language.
Re: Preview of Explore Logs, a new way to browse your logs without writing LogQL
#10I'll preface this with the fact I haven't look at Loki in a bit, so maybe this has changed. But I found the documentation needing a lot of work and the configuration for promtail to be obtuse and not very user friendly. I haven't used it for those reasons, not because of the query language.
Having used Loki/promagent etc, it was sort of a pain/nonintuitive to set up.