WLED VS loki

I think you're one of todays lucky 10000 [0] learning about WLED [1] today :)

[0] https://xkcd.com/1053/

[1] https://kno.wled.ge/

I’ll do you one better: Here is the WLED main site - they cover everything - however you want it for your vehicle is up to you! (If you want to see a truck I personally worked (with 2 other main guys doing the woodwork and wiring) on that was probably the “most expensive” project with these controllers, check out the SEMA entered “Realtree Stormtrooper truck” - a LOT of time went in to that and almost a year of prep, not a fan myself, but custom electronics are what I like doing)

Did you use the esp32.bin? If so, you should instead use ESP32-C3 here: https://github.com/Aircoookie/WLED/releases/download/v0.14.0/WLED_0.14.0_ESP32-C3.bin

Friend replaced all his govee cintrollers with WLED.

Multiple WLED controllers

I feel like I should start this post with a disclaimer. I tend to over-complicate things. Which means I'm making this post partly as a sanity check and partly to fill in some gaps in my kno.wled.ge

Look at WLED.

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.

I also needed to make a small patch to Promtail to make this work: https://github.com/grafana/loki/pull/10256

We don't pull logs, we forward logs to a centralized logging service.

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).

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

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

Loki