feat(aap): update tags on inferred spans for API Gateway #697
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
It updates tags for API Gateway Rest Proxy and HTTP API inferred spans, to enable discovery by both the APM Endpoint Catalog and the API Gateway Catalog:
From the RFC:

Motivation
This PR implements RFC-1081.
The goal is be able to use API Gateway lambda inferred spans for endpoint discovery and correlation in the AppSec API Catalog.
Testing Guidelines
Additional Notes
_dd.appsec.*meta and metrics are to be set in ddtrace: feat(aap): report AAP on lambda inferred spans dd-trace-py#15511http.user_agentintohttp.useragent, this is the tag specified in the "Span attributes" page of APM ( and the tag is used by the system-tests to correlate spans with requests, this is necessary to test this feature there)_dd.inferred_spanmetric, the backend filters inferred spans for the APM Catalog (and the AAP Catalog) based on this metric. It is already set by tracers for the API Gateway proxy inferred spans.Types of Changes
Check all that apply