Add steps to see relationship between Otel Service and AWS Memcached #19846
Conversation
|
|
|
|
|
Hi @Sanjalee-NewRelic 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. We will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 10 to 20 minutes). |
✅ Deploy Preview for docs-website-netlify ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Sanjalee-NewRelic
changed the title
| The memcacahed cluster entity to which the service is connecting should have the following tags: | ||
|
|
||
| * `aws.elasticache.configurationEndpointAddress` or `aws.elasticache.endpointAddress`: AWS connection endpoint of the memcached cluster matching with the span attribute `net.peer.name` of the service. | ||
| * `aws.elasticache.configurationEndpointPort` or `aws.elasticache.endpointPort`: Port number on which memcached cluster is running matching with the span attribute `net.peer.port` of the service. |
There was a problem hiding this comment.
Where do these tags come from? Does this require using a New Relic specific integration for AWS?
There was a problem hiding this comment.
@alanwest These tags are shown if the provider account in AWS integrations has metric streams enabled instead of API polling.
| * `net.peer.name`: AWS connection endpoint of the memcached clusterr ending with `cache.amazonaws.com` | ||
| * `net.peer.port`: Port number on which memcached cluster is running eg: `11211` |
There was a problem hiding this comment.
net.peer.name and net.peer.port are old attributes and they have been deprecated. There is probably still old instrumentation that produces them, but we're going to need to support the new attributes.
@jack-berg we should consider basing this rule on the apm.service.datastore.operation metric we generate. That way our entity relationship definitions do not need to support evolving semantic conventions.
src/content/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/opentelemetry/best-practices/opentelemetry-best-practices-resources.mdx
Outdated
Show resolved
Hide resolved
Please follow conventional commit standards
in your commit messages and pull request title.
Give us some context
Updated the opentelemetry resources with the information on how to see relationship between an opentelemetry instrumented service and AWS memcached cluster
links to related docs, screenshots, etc.