helm-charts
loki
Our great sponsors
helm-charts | loki | |
---|---|---|
19 | 80 | |
1,495 | 22,213 | |
3.4% | 4.0% | |
9.7 | 9.9 | |
5 days ago | 3 days ago | |
Smarty | Go | |
Apache License 2.0 | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
helm-charts
-
Loki with grafana.
Which helm Chart do you use? You should probably use this one https://github.com/grafana/helm-charts/tree/main/charts/loki-distributed
-
Grafana for K8S - configure dashboard access permissions
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 .
-
Spring Boot logging with Loki, Promtail, and Grafana (Loki stack)
Grafana Labs in its Helm repository provides chart that can install Loki stack also with other complementary tools like Logstash or Prometheus.
-
How to Monitor your k8s Persistent Volume Usage
Once you have this ready for your cluster install Grafana from Grafana helm chart from here
-
Promtail tenant doesn't apply
grafana/helm-charts/blob/main/charts/loki-stack/Chart.yaml
-
Grafana Helm Chart - LDAP not working
Using the helm chart values from values.yaml here https://github.com/grafana/helm-charts/blob/main/charts/grafana/values.yaml
- Ask HN: IT Security Checklist for Startups?
-
Query frontend for loki-stack
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.
-
helm value override doesn't work
from: https://github.com/grafana/helm-charts/blob/ef1cd8a48ab000137df980227745d1eeefcfbefb/charts/promtail/values.yaml
-
Helm looks in a different repository then the one I specify with a --repo flag
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"
loki
- Loki 3.0 Released
-
List of your reverse proxied services
I also needed to make a small patch to Promtail to make this work: https://github.com/grafana/loki/pull/10256
-
About reading logs
We don't pull logs, we forward logs to a centralized logging service.
-
loki VS openobserve - a user suggested alternative
2 projects | 30 Aug 2023
-
Logs monitoring with Loki, Node.js and Fastify.js
Over the past few months, I've been spending a lot of time creating dashboards on Grafana using Loki for MyUnisoft (the company I work for).
-
OpenObserve: Open source Elasticsearch alternative in Rust for logs. 140x lower storage cost
For log systems you generally don't migrate data. Logs lose value over time. What you want to do is to go ahead and start ingesting data into the new system (OpenObserve in this case) and slowly, the data in the old system will become stale and then you can retire it. However if you need to export logs anyhow, there is no straightforward way in loki to do this. You could run a script to query loki and export it to a file. If found this thread with a sample script - https://github.com/grafana/loki/issues/409
-
Config files of snaps?
That snap is woefully out of date. The upstream repo was recently updated to 2.8.2, but the snap stable channel has 2.4.1 from 18 months ago. https://github.com/grafana/loki/releases/tag/v2.8.2
-
i need to visualize all logs from remote dir
Loki
- Loki Helm charts that use DynamoDB
-
I can't recommend serious use of an all-in-one local Grafana Loki setup
I installed promtail a few weeks back and I ran into this bug, that has been outstanding for months: https://github.com/grafana/loki/issues/8663 (e.g. a fix had been written but had not been released):
Due to a buffering issue, Loki would exit in case of configuration error without printing any error message or anything at all
There is definitely something weird about how the project is run.
What are some alternatives?
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
ClickHouse - ClickHouse® is a free analytics DBMS for big data
syslog-ng - syslog-ng is an enhanced log daemon, supporting a wide range of input and output methods: syslog, unstructured text, queueing, SQL & NoSQL.
fluent-bit - Fast and Lightweight Logs and Metrics processor for Linux, BSD, OSX and Windows
zeek-clickhouse
Zabbix - Real-time monitoring of IT components and services, such as networks, servers, VMs, applications and the cloud.
VictoriaMetrics - VictoriaMetrics: fast, cost-effective monitoring solution and time series database
logging-operator - Logging operator for Kubernetes
ElastiFlow - Network flow analytics (Netflow, sFlow and IPFIX) with the Elastic Stack
vector - A high-performance observability data pipeline.
loki-multi-tenant-proxy - Grafana Loki multi-tenant Proxy. Needed to deploy Grafana Loki in a multi-tenant way