Closed cokiengchiara closed 3 years ago
@piontec can you write down the progress you made w Loki? 😁
I just made PoC run: the chart is imported to our repo, but not yet good enough to use.No work done on authorization and promtail.
@piontec Can already make Loki run w AWS. Not good, haven't tried it yet. Still missing promtail and multi-tenant for forwarding logs. Still quite a lot of work.
Closing. Real progress was tracked here: https://github.com/giantswarm/roadmap/issues/202
Towards https://github.com/giantswarm/roadmap/issues/175
Tasks tracked in https://github.com/giantswarm/roadmap/issues/202
Outcome:
A new cluster for running loki, logs coming in from external clusters (frontend and operations)
Tasks
https://github.com/grafana/loki/issues/2593 https://github.com/unguiculus/loki-helm-chart/
stretch goal
Context
From before Tue, 24. November 2020
Details, Background
From @jgsqware Thu, 29. Oct 2020: From Loki 2.0, we can now create alert on query on the logs ingested from loki. That would be really helpful to identify issues in nginx but not only. Yesterday we had issues in calico-kube-controller and calico even if the pods was still running. We had similar behavior with kube-proxy and kiam-server. Would be useful for us to have in place in the near future. It would easier to follow issues during upgrades.
Blocked by / depends on
As of Thu, 29. Oct 2020, from @glitchcrab - we're waiting for the Loki team to move the chart to it's own repo before we can realistically think about using it - lots of stuff will change with this and it should make it easier for us to use the upstream chart with minimal changes. https://github.com/grafana/loki/issues/2593