Christian Simon
Christian Simon
@knylander-grafana the ticket here was more created with the UI in mind, but yes ideally both.
cc @petethepig from our conversation
I would consider that a valid use case and a valuable addition to the component. Also do make sure to mention me in the PR so I won't miss it
Sorry about this, the bug is in fact in Pyroscope, we will have a fix released soon see the details in my message here: https://github.com/grafana/pyroscope/issues/4017#issuecomment-2737383551
Just to add a bit more context: For different components we use the [dskit/modules](https://pkg.go.dev/github.com/grafana/[email protected]/modules) package, you can find the original[ design for Cortex ](https://cortexmetrics.io/docs/proposals/generalize-modules/)(proper ancient). The role of the store-gateway...
Looking at the potential combinations and what I would expect: * storage.backend not configured and `target=all` (single binary): * As right now we won't initialize the store-gatway and shipper. *...
> Does this is a typo? Should it be storage.backend not configured and target!=all (micro services)? Yes it was, sorry for the confusion. > I was sure that the object...
This sounds like related to a bug, where we fail to display proper errors and break reloading after eBPF exits: do you mind giving this fix: https://github.com/grafana/alloy/pull/3381 a try.
One of the points to use distrolless is to reduce "atack surface" / "CVE noise". Adding as shell back would counteract this. I get your usecase, let's think about what...