5 ms·

I'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 configur

by wsatb 3y ago

I'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.

John23832 3y ago
Having used Loki/promagent etc, it was sort of a pain/nonintuitive to set up.
corytheboyd 3y ago
They gotta sell their managed cloud service somehow, I have always assumed that this is part of the sales strategy
liampulles 3y ago
Our team uses loki and I have to say I think their collected helm charts are pretty easy to use - my problem is more that it seems to be quite slow to run on-prem. Very often my loki query times out and I have to do more work filtering down the log lines or selecting a narrower time range. I'm kind of amazed the UI doesn't select small time ranges iteratively to build up the response, especially since I believe this is what the CLI does. Perhaps this is also part of their cloud offering provides and it is part of their marketing strategy. Not a good one because if we came down to the decision I would start by looking for something else from being p'ed off by Loki. But I guess it still works pretty well considering it is free.
- skrtskrt 3y ago
  Loki UI in Grafana Explore seems to only select 1000 lines by default for me? Also Loki on the backend splits/parallelizes requests if it can. The Grafana backend Mimir / Loki / Tempo products all appear to be architected pretty similar, and I'm more experienced operating Mimir, but the answer to read load often has to just do with right-sizing the deployment scale, and using caches aggressively.
blue_cookeh 3y ago
It's also incredibly easy to shoot yourself in the foot and rack up huge cloud bills - something we recently hit: https://github.com/grafana/loki/issues/8756 https://github.com/grafana/loki/issues/8756

by wsatb 3y ago

John23832 3y ago

Having used Loki/promagent etc, it was sort of a pain/nonintuitive to set up.

corytheboyd 3y ago

They gotta sell their managed cloud service somehow, I have always assumed that this is part of the sales strategy

liampulles 3y ago

Our team uses loki and I have to say I think their collected helm charts are pretty easy to use - my problem is more that it seems to be quite slow to run on-prem. Very often my loki query times out and I have to do more work filtering down the log lines or selecting a narrower time range. I'm kind of amazed the UI doesn't select small time ranges iteratively to build up the response, especially since I believe this is what the CLI does. Perhaps this is also part of their cloud offering provides and it is part of their marketing strategy. Not a good one because if we came down to the decision I would start by looking for something else from being p'ed off by Loki. But I guess it still works pretty well considering it is free.

skrtskrt 3y ago
Loki UI in Grafana Explore seems to only select 1000 lines by default for me? Also Loki on the backend splits/parallelizes requests if it can. The Grafana backend Mimir / Loki / Tempo products all appear to be architected pretty similar, and I'm more experienced operating Mimir, but the answer to read load often has to just do with right-sizing the deployment scale, and using caches aggressively.

blue_cookeh 3y ago

It's also incredibly easy to shoot yourself in the foot and rack up huge cloud bills - something we recently hit: https://github.com/grafana/loki/issues/8756 https://github.com/grafana/loki/issues/8756