Christian Simon

Support feature flags to propagate feature support from API backend to consumers

2

#### Is your feature request related to a problem? Please describe. Currently it is hard for consumers of the Pyroscope APIs to figure out when a new feature has become...

Migrate Pyroscope tracing to opentelemetry

1

#### Is your feature request related to a problem? Please describe. Pyroscope tracing is based on jaeger client and opentracing, which are deprecated. #### Describe the solution you'd like -...

This adds and adapts the grafana-cloud Github integration. Let me know what you think?

With dskit moving to otel/trace, we should also migrate our opentracing instrumentation to use otel/trace. See https://github.com/grafana/dskit/pull/681

This is a proof-of-concept attempt in grading similarity of profiles in order to detect an anomaly in a particular workload. For the implementation is used fairly naive approach: Take the...

V2: Query API incompatibility around missing time windows

2

#### Describe the bug A clear and concise description of what the bug is. When using the v2 mode, the API behaves directly, it seems to treat the time window...

We currently do always show the latest "master" source code, for golang standard library code in the Github integration. This causes quite awkward things, like comment are using CPU resources:...

We should add support for godeltaprof profile type within the Alloy bundled in https://github.com/grafana/pyroscope/blob/68c28f5d242d5637bd3e10144962e30b841d913b/operations/pyroscope/helm/pyroscope/templates/configmap-alloy.yaml#L20.

Provide better example configuration in repo

1

I think we should provide a better example config file in ./cmd/pyroscope/pyroscope.yaml. The [configuration page] in our docs seem to be tricky to understand, as they use a "reference name"...

With #651 it is possible to attach uprobes, but their results are currently merged together. This PR introduces the use of cookies (available from kernel 5.15+) to keep track of...