developer-roadmap VS loki

If you're starting your journey in web development, here is a roadmap to follow. Understand that Web development is not merely an extension of programming; it's a distinct field that requires a unique blend of coding and visual design skills. Embrace the importance of visual aesthetics from the get-go, and continuously work on improving your design sense. Trust me it will pay off in the long run, and you'll be able to create truly exceptional web experiences that not only function well but also look and feel amazing.

Github developer roadmaps (backend, frontend, cloud ...)

Roadmap.sh (https://roadmap.sh/)

Web Developer-Roadmap GitHub Link: developer-roadmap Crafted by kamranahmedse, this roadmap acts as a compass for developers navigating the vast landscape of technologies. Covering front-end, back-end, and DevOps, it aids developers in charting a learning path aligned with their goals.

✅ kamranahmedse/developer-roadmap: https://github.com/kamranahmedse/developer-roadmap

It may also be beneficial to start with a high-level overview of what there is to learn in a given area, to understand the overall lay of the land - and then use ChatGPT to dig deeper into selected topics. There are many good resources that provide such an overview, like roadmap.sh or my "Definitive Guide to Succeeding as a Professional Dev".

5. Roadmap

Equipment: Find out more about career paths in development at https://roadmap.sh/. For a detailed self-taught program, see Kamran Ahmed’s Computer Science Roadmap: https://roadmap.sh/computer-science.

Roadmap.sh serves as a comprehensive guide for developers planning their career paths and skill development. It offers structured roadmaps for different domains, helping developers navigate their professional journey.

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

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.