feat: Adding candidate and relationship btw OTel and kinesis stream

[AravindKumar8520]

We are establishing a relationship between OTel and AWS Kinesis Stream by using the ARN as the matching criterion. Users or customers from the OTel service need to manually send the ARN within the cloud.resource_id span attribute.

On the Cloud Monitoring platform side, we are associating tags with the aws.Arn for AWS Kinesis streams, ensuring that the collector.name is equal to cloudwatch-metric-streams.

The ARN is formatted as follows for a function: arn:${realm}:kinesis:${region}:${accountId}:stream/${StreamName}

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.

[naxhh]

this condition will relate anything that has a span with rpc.service=kinesis.

not sure I follow how we are making sure is ext-service/otel only

[AravindKumar8520]

If we're primarily receiving data in spans, i guess we should opt for:
origins: - Distributed Tracing
instead of
origins: - Opentelemetry
Currently, no pull request exists for APM to AWS Kinesis streaming. We anticipate that APM data will continue to arrive in span format; if it's in metrics, we'll use APM Metrics. Do we need to wait for the APM to AWS Kinesis stream PR?