You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using Container-Based APM on our Kubernetes cluster. We have the agent running in the cluster and dd-trace is enabled by annotations and environment variables, not via application code. It works great.
We have a Fastify API that makes multiple outgoing HTTP requests using axios. The issue we have is that the http.request resource names are named only by the HTTP method. We are not able to see metrics for different outgoing requests as they are all named GET or POST.
Is it possible to include the request URL in the resource name? The dd-trace-java does this, as we have this granularity for our Java APIs.
For incoming requests, fastify.request names the resources by request method and URL. We would love the same for outgoing requests.
Hi,
We are using Container-Based APM on our Kubernetes cluster. We have the agent running in the cluster and
dd-trace
is enabled by annotations and environment variables, not via application code. It works great.We have a Fastify API that makes multiple outgoing HTTP requests using
axios
. The issue we have is that thehttp.request
resource names are named only by the HTTP method. We are not able to see metrics for different outgoing requests as they are all namedGET
orPOST
.Is it possible to include the request URL in the resource name? The
dd-trace-java
does this, as we have this granularity for our Java APIs.For incoming requests,
fastify.request
names the resources by request method and URL. We would love the same for outgoing requests.node: 20.10
typescript: 5.7.2
fastify: 5.1.0
axios: 1.6.8
K8s:
admission.datadoghq.com/js-lib.version: v5.27.1
The text was updated successfully, but these errors were encountered: