parseable
loki
parseable | loki | |
---|---|---|
26 | 80 | |
1,705 | 22,213 | |
2.4% | 1.4% | |
9.2 | 9.9 | |
7 days ago | 6 days ago | |
Rust | Go | |
GNU Affero General Public License v3.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.
parseable
-
New release of Parseable [Log analytics system written in Rust] is now available
Checkout the release here: https://github.com/parseablehq/parseable/releases/tag/v0.7.0
-
OpenObserve: Elasticsearch/Datadog alternative in Rust.. 140x lower storage cost
How does this compare to Parseable?
https://github.com/parseablehq/parseable
First guess is that the underlying storage / query layer is pretty similar (Parquet + Datafusion), but OpenObserve has more built in use cases?
As an aside, it’s awesome that Datafusion’s existence and maturity makes launching a product with scalable analytical reads 10x easier than before and cool to see so many projects integrating it
-
Infino - Fast and scalable service to store time series and logs - written in Rust
Another cool rust project in this space for logs: https://github.com/parseablehq/parseable. Using Arrow for the memory format makes life easier for incorporating with other tools like Grafana.
- Lightweight ELK alternative for ingesting and analyzing local logs?
-
I can't recommend serious use of an all-in-one local Grafana Loki setup
- Visualize with Grafana
https://github.com/parseablehq/parseable
(founder here)
-
Parseable - an open source log observability platform
Hello DevOps community, we've been working on https://github.com/parseablehq/parseable for a while now. Would love to get any feedback, questions etc.
- Parseable – unify log data to Parquet on S3
- Show HN: Columnar store for fast, lightweight logging
- Lightweight, high performance logging engine based on Apache Arrow & Parquet
-
Syslog server
Maybe also take a look at: https://github.com/parseablehq/parseable
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?
openobserve - 🚀 10x easier, 🚀 140x lower storage cost, 🚀 high performance, 🚀 petabyte scale - Elasticsearch/Splunk/Datadog alternative for 🚀 (logs, metrics, traces, RUM, Error tracking, Session replay).
ClickHouse - ClickHouse® is a free analytics DBMS for big data
clp - Compressed Log Processor (CLP) is a free tool capable of compressing text logs and searching the compressed logs without decompression.
fluent-bit - Fast and Lightweight Logs and Metrics processor for Linux, BSD, OSX and Windows
kube-ns-suspender - A k8s controller that scales up and down namespaces on-demand with an embedded friendly UI and a Prometheus exporter. Inspired by kube-downscaler.
Zabbix - Real-time monitoring of IT components and services, such as networks, servers, VMs, applications and the cloud.
qryn - qryn is a polyglot, high-performance observability framework for ClickHouse. Ingest, store and analyze logs, metrics and telemetry traces from any agent supporting Loki, Prometheus, OTLP, Tempo, Elastic, InfluxDB and many more formats and query transparently using Grafana or any other compatible client.
VictoriaMetrics - VictoriaMetrics: fast, cost-effective monitoring solution and time series database
pino - 🌲 super fast, all natural json logger
ElastiFlow - Network flow analytics (Netflow, sFlow and IPFIX) with the Elastic Stack
tracing - Application level tracing for Rust.
loki-multi-tenant-proxy - Grafana Loki multi-tenant Proxy. Needed to deploy Grafana Loki in a multi-tenant way