openobserve
loki
openobserve | loki | |
---|---|---|
38 | 81 | |
9,648 | 22,265 | |
7.6% | 1.6% | |
9.9 | 9.9 | |
6 days ago | 7 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.
openobserve
-
Show HN: OneUptime – open-source Datadog Alternative
Lot of interesting OSS observability products coming out in recent years. One of the more impressive(and curious for many reasons) IMHO is OpenObserve: https://github.com/openobserve/openobserve .
As opposed to just a stack, they are implementing just about the whole backend shebang from scratch.
-
Indexing one petabyte of logs per day with Quickwit
in case it matters to others, https://github.com/openobserve/openobserve/tree/v0.7.0 is the last Apache2 licensed copy before they went AGPL with 0.7.1
https://github.com/openobserve/openobserve/blob/v0.7.0/.env.... is some "onoz" for me, but just recently someone submitted https://github.com/aenix-io/etcd-operator to the CNCF sandbox so maybe things have gotten better around keeping that PoS alive
-
Apache Superset
eCharts is awesome. We moved from plotly after using it for several months to echarts at https://github.com/openobserve/openobserve and are super happy.
-
Logdy.dev – web based logs viewer UI for local development environment
Wouldn't make more sense to have the same observability stack on production and development? For instance, open-observe is also a single binary that provides UI for logs, metrics and traces, although every log producer would have to be properly configured and routing to it.
Another idea: maybe chrome dev-tools could be repurposed to display server logs instead of client logs, somehow [2].
--
1: https://github.com/openobserve/openobserve
2: https://chromedevtools.github.io/devtools-protocol/
-
Did OpenTelemetry deliver on its promise in 2023?
It doesn't read from files unfortunately, but https://openobserve.ai/ is very easy to set up locally (single binary) and send otel logs/metrics/traces to.
Here's how I run it locally for my little shovel project - https://github.com/bbkane/shovel#run-the-webapp-locally-with... .
Also linked from that README is an Ansible playbook to start OpenObserve as a systems service on a Linux VM.
Alternatively, see the shovel codebase I linked above for a "stdout" TracerProvider. You could do something like that to save to a file, and then use a tool to prettify the JSON. I have a small script to format json logs at https://github.com/bbkane/dotfiles/blob/2df9af5a9bbb40f2e101...
-
Everything is working :(
Implement a monitoring stack, or openobserve for an all-in-one package.
-
Windows alternative to Graylog?
I would recommend you take a look at OpenObserve (https://github.com/openobserve/openobserve ). It's free and open source and can do all you asked and more with far lower resource utilization. It's the easiest to run of any log system that you can find. Can capture windows and linux logs. Also compresses them heavily (30-60x, YMMV). 100 GB ingested logs can be 3 GB stored.
- Show HN: Monitor your webapp with minimal setup
-
μMon: Stupid simple monitoring
I have used https://github.com/openobserve/openobserve in several hobby projects and liked it. It's an all-in-one solution. It's likely less featureful than many others but a single binary and everything in one place pulled me in and worked for me so far.
Not affiliated, I just like the tool.
-
Show HN: HyperDX – open-source dev-friendly Datadog alternative
A good one. A lot is being built on top of clickhouse. I can count at least 3 if not more (hyperdx, signoz and highlight) built on top of clickhouse now.
We at OpenObserve are solving the same problem but a bit differently. A much simpler solution that anyone can run using a single binary on their own laptop or in a cluster of hundreds of nodes backed by s3. Covers logs, metrics, traces, Session replay, RUM and error tracking are being released by end of the month) - https://github.com/openobserve/openobserve
loki
-
Release Radar · April 2024 Edition: Major updates from the open source community
It's like Prometheus, but for logs. Okay it's not really to do with the Norse or Greek gods, instead Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by the open source project Prometheus. Built by Grafana Labs, Loki is designed for ease of use. Instead of indexing the contents of the logs, Loki provides a set of labels for each log stream. The latest update includes query acceleration with Bloom filters, native OTel support, Helm charts, and more. Check out the changelog for all the major changes and deprecations.
- 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
What are some alternatives?
graylog - Free and open log management
ClickHouse - ClickHouse® is a free analytics DBMS for big data
quickwit - Cloud-native search engine for observability. An open-source alternative to Datadog, Elasticsearch, Loki, and Tempo.
fluent-bit - Fast and Lightweight Logs and Metrics processor for Linux, BSD, OSX and Windows
hyperdx - Resolve production issues, fast. An open source observability platform unifying session replays, logs, metrics, traces and errors powered by Clickhouse and OpenTelemetry.
Zabbix - Real-time monitoring of IT components and services, such as networks, servers, VMs, applications and the cloud.
parseable - Parseable is a log analytics system platform for modern, cloud native workloads
VictoriaMetrics - VictoriaMetrics: fast, cost-effective monitoring solution and time series database
Collectd - The system statistics collection daemon. Please send Pull Requests here!
loki-multi-tenant-proxy - Grafana Loki multi-tenant Proxy. Needed to deploy Grafana Loki in a multi-tenant way
openobserve-chart - Simplified Helm chart for single-node OpenObserve
ElastiFlow - Network flow analytics (Netflow, sFlow and IPFIX) with the Elastic Stack