feat: Enhance Entity Relationships - for APM and OTel to APPSYNC API

[vinaykonatala]

Relevant information

APM to APPSYNC API relationship
We are establishing a relationship between APM and AWS APPSYNC API by using the httpUrl as the matching criterion.

On the Cloud Monitoring platform side, we are associating tags with the Http.Url for AWS appsync api, ensuring that the collector.name is equal to cloudwatch-metric-streams.

The ARN is formatted as follows for a function: [a-z0-9]{25}.appsync-api.us-east-2.amazonaws.com

Otel to APPSYNC API relationship
We are establishing a relationship between APM and AWS APPSYNC API by using the httpUrl as the matching criterion. Users or customers from the APM service need to manually send the ARN within the httpUrl span attribute.

On the Cloud Monitoring platform side, we are associating tags with the Http.Url for AWS appsync api, ensuring that the collector.name is equal to cloudwatch-metric-streams.

The ARN is formatted as follows for a function: [a-z0-9]{25}.appsync-api.us-east-2.amazonaws.com

Checklist

• I've read the guidelines and understand the acceptance criteria.
• The value of the attribute marked as identifier will be unique and valid.
• I've confirmed that my entity type wasn't already defined. If it is I'm providing an explanation above.

[nr-cmorenoin]

Relationship blocked in production by FF https://featureflag.datanerd.one/flags/10463/edit