feat: Adding candidate and relationship btw OTel and kiness delivery stream #1
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.
Relevant information
We are establishing a relationship between OTel and AWS Kinesis delivery 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 firehouse delivery 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
identifier
will be unique and valid.