operation: Make `loki-mixin` available to non-jsonnet users as well.

[kavirajk]

Currently Loki operators who are using jsonnet can only benefit from dashboards and alerts from loki-mixin. We should support those dashboards and alerts for non jsonnet users as well.

Something similar to what mimir does with mimir-mixin-compiled.

[trevorwhitney]

:+1: strongly agree

[pracucci]

I also invite you to write some doc on how to install it. You could get some inspiration from here: https://github.com/grafana/mimir/tree/main/docs/sources/operators-guide/visualizing-metrics

[sureshgoli25]

I was searching for instructions of loki-mixin in kubernetes. But, as of now no look.

[sureshgoli25]

I am quite new to loki and mixin dashboards. We are using loki-distributed helm chart in our environment. And it seems to be the new mixin pre complied dashboars under mixin-complied folder are not working in our environment. Since, we are not getting value for cluster varaible. Most of the fields are not refelcting the data.

Kind of googling myself now, how to customize the complied dashboards to make to use for the loki-distributed helm charts (oss).

Attached images for reference.

[pracucci]

I am quite new to loki and mixin dashboards. We are using loki-distributed helm chart in our environment. And it seems to be the new mixin pre complied dashboars under mixin-complied folder are not working in our environment. Since, we are not getting value for cluster varaible. Most of the fields are not refelcting the data.

I created a dedicated issue to keep track of it: https://github.com/grafana/loki/issues/6266

[aslafy-z]

It looks like these dashboard where made available at https://monitoring.mixins.dev/loki/.

[stale[bot]]

Hi! This issue has been automatically marked as stale because it has not had any activity in the past 30 days.

We use a stalebot among other tools to help manage the state of issues in this project. A stalebot can be very useful in closing issues in a number of cases; the most common is closing issues or PRs where the original reporter has not responded.

Stalebots are also emotionless and cruel and can close issues which are still very relevant.

If this issue is important to you, please add a comment to keep it open. More importantly, please add a thumbs-up to the original issue entry.

We regularly sort for closed issues which have a stale label sorted by thumbs up.

We may also:

• Mark issues as revivable if we think it's a valid issue but isn't something we are likely to prioritize in the future (the issue will still remain closed).
• Add a keepalive label to silence the stalebot if the issue is very common/popular/important.

We are doing our best to respond, organize, and prioritize all issues but it can be a challenging task, our sincere apologies if you find yourself at the mercy of the stalebot.

[aslafy-z]

Un-stale please