Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CPU and memory allocation continuous profiler #3074

Open
Kielek opened this issue Nov 7, 2023 · 1 comment
Open

CPU and memory allocation continuous profiler #3074

Kielek opened this issue Nov 7, 2023 · 1 comment
Milestone

Comments

@Kielek
Copy link
Contributor

Kielek commented Nov 7, 2023

Feature Request

Note
AlwaysOn Profiler is the name used as a product feature in Splunk. Broadly it is more known as a continuous profiles. It takes small portion of data every few seconds/events.

Implement CPU and memory profiler for .NET based on description in Splunk repository:

Most of the native code is stored under: https://github.com/signalfx/signalfx-dotnet-tracing/blob/main/tracer/src/Datadog.Trace.ClrProfiler.Native/always_on_profiler.cpp (and other prefixed by always_on_*).
Most of the managed code part: https://github.com/signalfx/signalfx-dotnet-tracing/tree/main/tracer/src/Datadog.Trace/AlwaysOnProfiler
Integration tests: https://github.com/signalfx/signalfx-dotnet-tracing/blob/main/tracer/test/Datadog.Trace.ClrProfiler.IntegrationTests/AlwaysOnProfilerPprofTests.cs
Tests application (covers all .NET languages): https://github.com/signalfx/signalfx-dotnet-tracing/tree/main/tracer/test/test-applications/integrations/Samples.AlwaysOnProfiler

@pellared
Copy link
Member

pellared commented Nov 8, 2023

I propose to add a pprof exporter as it could be useful for both the users as well as OTLP Profiler SIG for reference.

@Kielek Kielek changed the title CPU/Allocation profiler CPU/Allocation continuous profiler Nov 8, 2023
@pellared pellared changed the title CPU/Allocation continuous profiler CPU and memory allocation continuous profiler Nov 8, 2023
@pjanotti pjanotti added this to the vNext milestone Nov 15, 2023
@Kielek Kielek mentioned this issue Jan 2, 2024
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants