Skip to content

Starting profilere from otel exteension + starting from custom classsloadeer is unsupported #76

Description

@korniltsev-grafanista

afteer #68
There is still a configuration that I think will not work: when otel extension actually starts vendored profiler and then spring boot jar tries to start profiler again. It likely will not work and idk how to make it work without breaking changes in pyroscope-java. I will create an issue for this case.
imo this should be documented as an unsupported configuration and issue a warning.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions