There is very much an alternative. Looking at the execution of your code should never alter its fundamental performance the way otel is built to do. This was a solved problem at least a decade and a half ago, but the cool kids decided to reinvent the wheel, poorly.

https://news.ycombinator.com/item?id=45845889

▲

PunchyHamster 2 days ago | parent | next [-]

dtrace was meant for entirely different use, and it's not a replacement for otel

Otel was made to basically track the request execution (and anything that request triggers) across multiple apps at once, not to instrument an app to find slow points

▲

nothrabannosir 2 days ago | parent | next [-]

To OP’s credit though the latter is exactly what every single piece of otel documentation pushes you to do. Using only the manual spans api is an exercise in api docs spelunking and ignoring “suggested best practices” and “only do this if everything else has failed for you”.

▲

kchoudhu 2 days ago | parent | prev [-]

We should be using USDTs to emit trace ids that can be consumed by dtrace and shoved into whatever backend we want for tracing.

▲

masterj 2 days ago | parent | next [-]

Why don’t you try that, convert the output to OTLP and then write about it?

▲

ok_dad 2 days ago | parent | prev [-]

What’s a USDT? All I can find on Google is crypto garbage.

	▲	tofflos 2 days ago \| parent [-]
		https://illumos.org/books/dtrace/chp-usdt.html#chp-usdt

▲

csomar 2 days ago | parent | prev [-]

That's just one dimension to telemetry. For my use case, for example, I need distributed tracing; which is a fancy word for correlated logs.