Continuous Profiler does not support macOS

[nuxzero]

Current behaviour

I'm upgrading ddtrace from version 0.45 to 1.22.0 and testing with macOS agent on my local, but profiling data not showing and get the below warning that it's not supported macOS. However, it used to work with version 0.45.

W, [2024-05-02T13:30:42.093230 #7931] WARN -- ddtrace: [ddtrace] Profiling was requested but is not supported, profiling disabled: Your ddtrace installation is missing support for the Continuous Profiler because macOS is currently not supported by the Datadog Continuous Profiler. Get in touch with us if you're interested in profiling your app!

Expected behaviour

It should show profiling data from the trace.

Steps to reproduce

1. Go to APM Traces
2. Click a trace
3. Click Code Hotspots
4. Click Breakdown tab

How does datadog help you?

Environment

• datadog version: Datadog Agent 7.52.1
• Configuration block (Datadog.configure ...): initializers/datadog.rb file

  c.service = service_name
  c.version = service_version
  c.env = service_env
  c.profiling.enabled = profiling_enabled

  config.ru file

  require "datadog/profiling/preload"
  ...

• Ruby version: 2.7.4
• Operating system: macOS 14.4.1
• Relevant library versions: ddtrace 1.22.0

[ivoanjo]

Hey @nuxzero, thanks for getting in touch!

Indeed back in the 0.x series the profiler was able to work on macOS (with some limitations -- such as not supporting cpu-time).

What happened was during the 1.x series we rewrote most of the profiler, and the rewritten profiler does not currently work on macOS, other than inside docker. (There's some support for development, but it needs a few manual steps)

We don't often have requests for macOS support -- can you tell us more about your use-case?

[nuxzero]

Thank you for replying @ivoanjo . Right now I’m enabling profiler in my service and I would like to test it on my local environment before deploying it. However, I will try with Docker agent instead.

[ivoanjo]

Got it! It should work seamlessly within docker, do let us know if you run into any issues.

Testing the profiler locally is something we ourselves make use of -- hence my mention of there being some support we use for development. Unfortunately, there's a few roadblocks to be solved (mostly around distribution) before we can support it officially again.

[ivoanjo]

I've updated the ticket title and marked it as a feature request, since we explicitly are not supporting macOS in the profiler for now, BUT we're definitely wanting to know about folks that miss this + what's your use case :)