diagrams VS loki

diagrams - Diagram as Code.

Ja sam koristio ovo: https://diagrams.mingrammer.com/

That’s another option: https://diagrams.mingrammer.com Guessing with IaC done with Pulumi (Python) and this, it could pretty powerful and automatically generated.

Diagrams allow you to draw cloud system architectures using Python code.

I use excalidraw a lot for short conversations. If I have to go into major detail I use diagrams https://diagrams.mingrammer.com

Any codebase out there, written in go, that offers somewhat same philosophy as https://github.com/mingrammer/diagrams? TLDR; Generate photographic diagrams from code.

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

Loki

If you use Loki as the default logging driver with Docker and the Loki container shuts down, the rest of your containers will freeze up. This has been an issue for almost 3 years.

https://github.com/grafana/loki/issues/2361

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.

Loki docs are here: https://github.com/grafana/loki/tree/main/docs/sources they are OSS.

The last contributor to the docs was an hour ago (at time of writing this comment) and came from a maintainer not employed by Grafana Labs.

Looking down the recent commits I see lots of activities from non-Grafana employees that have been accepted.

If there are specific issues with contributing docs or code please do point me towards them.

There are also log forwarding tools like promtail and fluentbit that can be used to both ship logs to something like Loki and produce metrics.