Custom Tracing Implementation

[timl2415]

Hi, we are working on an application that makes heavy use of work queues. We'd like some way to monitor work queue events to optimize timings/priorities etc. I was looking into user tracing configurable via:
https://docs.zephyrproject.org/latest/services/tracing/index.html

However, the user tracing interface seems pretty lacking in general, only thread tracing APIs seem user-definable while all other APIs are effectively no-opped. The user tracing sample only shows how to define these thread tracing APIs. This page https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.4.99-dev1/zephyr/guides/tracing/index.html seems to hint at some way for applications to redefine tracing macros but no examples exist. Is there a way to accomplish this without patching the SDK?

Thanks,

Tim

[timl2415]

In addition to the above it seems like there's no tracing around the actual handling of work items in the work queue, only around the APIs that feed into the work queue externally (k_work_submit, k_work_cancel etc.). So even with a fully implemented tracing backend it would be difficult to see which work items are getting processed.