Open ranayash45 opened 3 days ago
Hi @ranayash45,
Thanks for the questions. The span that you see for API Gateway in your lambda traces is what we refer to as an "inferred span". This is because API Gateway itself is not creating the span. Instead, it is created in the Datadog Extension inside your lambda function.
In API Gateway for example, the inbound event payload includes a field for the time in which the request was started. The Extension grabs this value and, using other attributes from your inbound event payload, then creates the inferred span.
That said, as far as obfuscating tags on your API Gateway spans, since these are created and sent to the backend by the Extension, which is a special build of the Datadog Agent, you should be able to use any of our documented obfuscation methods on your span tags.
It seems like using the DD_APM_REPLACE_TAGS
environment variable will do exactly what you're looking for.
Let us know here if that works out for you and if you need any more help. Always happy to assist.
DD_APM_REPLACE_TAGS works well. thanks a lot :) Can we change service name for API-Gateway?? ( I am checking which attribute name needs to be replaced but not getting much on that)
Hi Datadog Team,
I have question regarding integration of dd-trace-go library and aws-api gateway.
Infrastructure details:-
using AWS Lambda function with DD-EXTENSION-LAYER:58. having AWS API Gateway in front of lambda.
Question:- 1 - Is AWS API Gateway using Lambda extension to push API Gateway Span along with Lambda Span?? 2 - Is there any way to modify that before pushing it to Datadog?
3 - Please provide basic workflow, how it is pushing data to Datadog? (already aware about configurations).