logging-operator VS helm-charts

Learn about how the Logging operator (CNCF Sandbox project) enables multi-tenant scenarios:

Banzai moved it out into a dedicated kube-logging organization on Github, at https://github.com/kube-logging/logging-operator 4.0 released a few weeks ago.

Shameless plug, I recommend you give a shot to https://github.com/banzaicloud/logging-operator - I am one of the maintainers.

Logging Operator Helm Chart - https://github.com/banzaicloud/logging-operator

There is even whole projects setup to solve the horrible nature that is efk / elk. See https://github.com/banzaicloud/logging-operator

How does this compare to/differ from the Banzai Logging operator?

Which helm Chart do you use? You should probably use this one https://github.com/grafana/helm-charts/tree/main/charts/loki-distributed

We were able to keep this config in Grafana UI but if the pod (K8S) is fail the details is deleted, we are using latest prom helm .

Grafana Labs in its Helm repository provides chart that can install Loki stack also with other complementary tools like Logstash or Prometheus.

Once you have this ready for your cluster install Grafana from Grafana helm chart from here

grafana/helm-charts/blob/main/charts/loki-stack/Chart.yaml

Using the helm chart values from values.yaml here https://github.com/grafana/helm-charts/blob/main/charts/grafana/values.yaml

Hey everyone! This is probably an easy question for those of you with experience. I’m using helm to install loki-stack and cannot figure out how to enable the query frontend with the Helm chart.

from: https://github.com/grafana/helm-charts/blob/ef1cd8a48ab000137df980227745d1eeefcfbefb/charts/promtail/values.yaml

helm3 upgrade --install grafana grafana --dry-run --repo https://grafana.github.io/helm-charts --wait Release "grafana" does not exist. Installing it now. Error: failed to download "https://github.com/grafana/helm-charts/releases/download/grafana-6.16.14/grafana-6.16.14.tgz"