4 ms·

So this is something like mtail [1], with the ability to also drill down into the raw logs, and integrated into Grafana? Sounds great! We're heavy users of Gra

So this is something like mtail [1], with the ability to also drill down into the raw logs, and integrated into Grafana? Sounds great! We're heavy users of Grafana, Graphite, Prometheus, and Elasticsearch, and while the latter started in a BI role it's expanded to take on pretty much anything we can throw at it. However, there's still tons of system and service logs we're not gathering yet, because the effort to get them to Elasticsearch and store/maintain them is not worth it, especially since the value is not always clear until well after the pipeline is set up. I'm definitely excited to see what loki can do for us, and just upgraded one of our test Grafanas to nightly to start playing with Explore, looks great! [1] https://github.com/google/mtail https://github.com/google/mtail

netingle 8y ago
Exactly! In fact, we're moving to use some of mtails libraries and functionality [0]. The main difference is we do centralise, scalable persistence of the logs themselves, wheres IIUC mtail just processes them and exports metrics. Thanks for the feedback, and feel free to reach out with any questions. [0] https://github.com/grafana/loki/pull/51 https://github.com/grafana/loki/pull/51
davkal 8y ago
Grafana Explore author here. It's still in Beta and would love feedback. Simply open an issue at [0]. What we tried to get right is the seamless switch from a Prometheus to Loki where it's retaining the labels of the query to essentially find the logs that come from the same e.g., "job". The assumption is that you need to be consistent with your relabelling rules of Prometheus and Loki. [0] https://github.com/grafana/grafana/issues/new https://github.com/grafana/grafana/issues/new