Christian Simon

Our dotnet sdk actually doesn't support inuse memory profiles (AFAIK). I do think we have some other thing interfering here. Do you mind sharing the Pyroscope version you are using?

@devmentality yes I agree with your suggestions and would more than welcome a PR from you ❤️ Not fully sure if this has drawbacks that I missed but, I would...

Yes thanks for your PR, is released as v1.12.0

Yes fully agreed. We haven't gotten around to it yet, and it might be a couple more weeks until we get to it. If you feel up for it I...

The only thing you can control right now is the log level, so an environment variable won't solve you issue completely: `PYROSCOPE_LOG_LEVEL=error`. See also https://grafana.com/docs/pyroscope/latest/configure-client/language-sdks/java/#configuration-options. Customizable logger were requested before,...

We are aware that lts kernel versions 6.1.y starting with 6.1.113 and 6.6.y starting with 6.6.55 have this uprobe regression. I proposed adding the fix to the stable kernel: https://lore.kernel.org/stable/[email protected]/T/#u...

I do think this has to do how we treat the timeline and how we've chosen the wrong unit for cumulative profile types. So we need to address this slightly...

@swar8080 let us know if https://github.com/grafana/alloy/pull/3630 improves the situation for you an if this can be closed. We might be able to avoid disk use all together, by e.g named...

I have started with four internal dashboards and the rules rely relies on in #4525. Let me know if those are usable for your purposes and which areas you lack...

I think there is a bigger question about if duration should be determined like in v1 where it is basically `end - start` of the query parameters or if it...