Ed here, (@slim-bean on github), one of the original authors and lead of the Loki project.
The criticisms brought by Chris are valid, and it's good feedback. I just wish it was done so in a more constructive manner.
I personally know what Loki is capable of, I've watched it grow from something tiny to something I'm incredibly proud of and in awe of.
I run Loki on several Raspberry Pi's ingesting 20-100GB a day, I also run Loki clusters on thousands of cores ingesting hundreds of TB's a day. It's an amazingly flexible and capable project built by an amazing team by a company I'm incredibly proud to work for.
That being said....
> Loki doesn't feel like it's been built to be operable by people who don't know its code and its internal details
How true this is... while I know for a fact there are hundreds to thousands of folks out there who are successfully running Loki (and thank you to those who share your success stories, it means the world to us), it can be very rough around the edges...
But we are working hard to improve this, we are doing the best we can.
All I really ask is for folks who want to give feedback about Loki, PLEASE DO! but please be patient.
The author of this article says they tried to work with us to improve Loki and that it didn't work out. I'm truly sorry for that, these posts are full of constructive feedback and I would really love to see this put into issues and pull requests to make the project better.
As a counterpoint to the article, I use loki, grafana, and promtail to manage logs for 5 hosts running a number of different services. I have had absolutely no issues for the last year. I haven't run into any of the issues the OP did. I suppose it's possible that he's running at a scale where certain problems happen that I won't see with my setup.
But honestly I sort of assumed that if you are going to manage hundreds of machines you should probably look at the more scalable configurations anyway. But if you are just doing a handful of machines it's more than capable in the local store only version.
2018 MBP, Using it on battery, saw I was at 20% plugged it in, noticed it was running like crap so I started closing applications, restarted it.
Still running like crap after reboot, also noticed fans were not spinning figured maybe an SMC reset is in order when
I realized it was at 2% battery, had not been charging, status said it was plugged in but not charging.
Powered it off to do the SMC reset and I can get nothing from it now, not a thing, no sounds, no signs of life, no fans, no apple logo, no clicks from the trackpad.
I think this qualifies as a brick.
The criticisms brought by Chris are valid, and it's good feedback. I just wish it was done so in a more constructive manner.
I personally know what Loki is capable of, I've watched it grow from something tiny to something I'm incredibly proud of and in awe of.
I run Loki on several Raspberry Pi's ingesting 20-100GB a day, I also run Loki clusters on thousands of cores ingesting hundreds of TB's a day. It's an amazingly flexible and capable project built by an amazing team by a company I'm incredibly proud to work for.
That being said....
> Loki doesn't feel like it's been built to be operable by people who don't know its code and its internal details
How true this is... while I know for a fact there are hundreds to thousands of folks out there who are successfully running Loki (and thank you to those who share your success stories, it means the world to us), it can be very rough around the edges...
But we are working hard to improve this, we are doing the best we can.
All I really ask is for folks who want to give feedback about Loki, PLEASE DO! but please be patient.
The author of this article says they tried to work with us to improve Loki and that it didn't work out. I'm truly sorry for that, these posts are full of constructive feedback and I would really love to see this put into issues and pull requests to make the project better.