logutils
loki
Our great sponsors
| logutils | loki | |
|---|---|---|
| 1 | 80 | |
| 362 | 22,149 | |
| 0.0% | 3.7% | |
| 0.0 | 9.9 | |
| about 1 year ago | 5 days ago | |
| Go | Go | |
| Mozilla Public 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.
logutils
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?
log - Structured logging package for Go.
ClickHouse - ClickHouse® is a free analytics DBMS for big data
logrus - Structured, pluggable logging for Go.
fluent-bit - Fast and Lightweight Logs and Metrics processor for Linux, BSD, OSX and Windows
go-log - a golang log lib supports level and multi handlers
Zabbix - Real-time monitoring of IT components and services, such as networks, servers, VMs, applications and the cloud.
sqldb-logger - A logger for Go SQL database driver without modifying existing *sql.DB stdlib usage.
VictoriaMetrics - VictoriaMetrics: fast, cost-effective monitoring solution and time series database
logex - An golang log lib, supports tracking and level, wrap by standard log lib
ElastiFlow - Network flow analytics (Netflow, sFlow and IPFIX) with the Elastic Stack
Onelog - Dead simple, super fast, zero allocation logger for Golang
loki-multi-tenant-proxy - Grafana Loki multi-tenant Proxy. Needed to deploy Grafana Loki in a multi-tenant way