I noticed dtrace patch is no longer maintained (https://github.com/openresty/openresty/commit/f17fe6edc142a82411637c058240a30ec33242ff), what is the reasoning behind?

elvin.efendiyev · 2020-03-04T04:06:55+00:00

Hi, Thanks for the quick response. I am sorry I did not understand how the above code will replace the redirect_uri. Could you please help me with this. Re...

I noticed dtrace patch is no longer maintained (https://github.com/openresty/openresty/commit/f17fe6edc142a82411637c058240a30ec33242ff), what is the reasoning behind?

elvin.efendiyev

Hello,

I noticed `dtrace` patch is no longer maintained: https://github.com/openresty/openresty/commit/f17fe6edc142a82411637c058240a30ec33242ff

Can you explain what's the reasoning behind? Does this mean https://github.com/openresty/openresty-systemtap-toolkit will no longer be useful?

We are looking into reimplementing the tracing/profiling tools in https://github.com/openresty/openresty-systemtap-toolkit using eBFP/https://github.com/iovisor/bpftrace so that we

can use them against Openresty processes running in containers. But without the dtrace patch (USDT probes) that's being discontinued it is not possible.

agentzh

Hello!

> I noticed `dtrace` patch is no longer maintained: https://github.com/openresty/openresty/commit/f17fe6edc142a82411637c058240a30ec33242ff
> Can you explain what's the reasoning behind?

Because it's just too painful to resolve all those merge conflicts
every time we sync with upstream nginx core changes.

> Does this mean https://github.com/openresty/openresty-systemtap-toolkit will no longer be useful?

Actually that open source project does not really depend on the dtrace
patch much. And it is also superseded by OpenResty XRay anyway and we
don't need the dtrace patch in the OpenResty core in OpenResty XRay at
all:

https://openresty.com/en/xray/

Best,
Yichun