3 ms·

Loki author here: got some ideas? We’re all ears!

• mgbmtl 7y ago
  Hi! Any plans to release binaries? If I am currently using 1% of ELK features (I use it for simple log aggregation of servers), but not k8s, would you still recommend loki?
  • netingle 7y ago
    Yes we do! Plan on cutting v0.1 in the next week or so, kubecon kinda got in the way... I’ll work on adding some binaries to that - what platform you looking for?
    • nickserv 7y ago
      Not the OP but in the same situation. I run Debian 9 on my servers, would be great to have some debs to try it out. Thanks!
    • mgbmtl 7y ago
      Great, thank you! I look forward to testing it. I also use Debian 9 (or stable, slowly moving towards Debian 10 which will soon be released).
    • Hansi 7y ago
      +1 RedHat 7 and 8.
• olafure 7y ago
  Alerting on certain log entries, please :) Even a simple label match would be a good start.
• tmzt 7y ago
  Reading up on Loki, it seems it lacks full-text search, prefering something called 'distributed grep'. I'm also looking at sonic, which is a new full-text search engine in rust with less overhead than Elasticsearch. It's lacking a gui focused on log search. Could they work together somehow, maybe as an alternative backend to you distributed grep? Sonic does not store the original content, so it could store a reference into your compressed chunk.
• physicles 7y ago
  Allow me to view log lines nearby a specific line that showed up in a search, kind of like grep -C n. Use case is that I’m seeing HTTP 500s from my web service. I can isolate the log lines for those requests, but if I want to see the extra lines (perhaps for a crash) that led up to it, I have to remove my search filter and manually set a time range that’s small enough that it returns fewer than 1000 lines. That, and retention policies. I just had a disk fill up because Loki keeps saving data. That said, I’ve been using Loki for several months and I love it. Keep up the great work!