Enable the experimental profiles signal support in the OTel Collector by building or using a collector-contrib binary that includes the otlp receiver with profiles support
Configure the application SDK or profiling agent to emit profiles over OTLP using the profiles signal endpoint
Add a pyroscope exporter to the Collector exporters block and configure the Pyroscope endpoint URL and tenant ID
Wire a profiles pipeline in the service pipelines block connecting the otlp receiver to the pyroscope exporter
Verify profiles appear in the Pyroscope UI and confirm that trace IDs from correlated spans are linked in the profile metadata
Known gotchas
The OTel profiling signal is experimental and not yet included in the stable Collector distributions; the collector-contrib or a custom build is required
Profile data serialization uses a different protobuf schema than traces or metrics; existing OTLP exporters that predate the profiling signal extension do not forward profiles
Correlating profiles with traces requires that both the profiling SDK and the tracing SDK use the same trace and span ID at the point of profile capture
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp