HTTP PUT and PATCH Data and headers

[nikalemdzievski]

Describe the feature you'd like

We don't have PUT or PATCH data when span concerns PUT or PATCH requests.
There is a functionality for POST tho, so I was wondering if there was any specific reason why PUT and PATCH are not implemented.

Is your feature request related to a problem?

No

Describe alternatives you've considered

One can always add this data manually by extending the span but it will be nice to have this supported out of the box same as for POST requests.

[PROFeNoM]

Hello @nikalemdzievski!

Thank you for submitting your feature request 😃

Could you please provide some additional information to scope your request better? Specifically, can you share your use case for this feature? For example, are you using Guzzle? Additionally, what do you expect to see in the spans? Would something like http.patch.key -> val work for you?

I appreciate your help!

[nikalemdzievski]

Hey @PROFeNoM !

thanks for getting back to me, I appreciate your patience.

This would come in handy when we wanna debug a particular request. Often the performance or bugs are isolated to specific users, resources, or parameters. For example, consider updating a user. There is a bunch of data that is coming in the body that is not visible on Datadog.
What I am hoping to see is the same functionality and format as the DD_TRACE_HTTP_POST_DATA_PARAM_ALLOWED functionality. Key http.patch.key -> val will work just fine. I think the current format for POST is something like this: http.request.key=value (based on the docs).

We use Laravel as a framework which uses Guzzle in the background.
Let me know if I can provide more information.

Thank you,
Nikola.