Trying to reduce the entity relationship data gaps when APM applications use AWS services. Need to explore what entity relationship data can be captured and emitted from the agent when either AWS_ELASTICACHE_REDIS_CLUSTER or AWS_ELASTICACHE_MEMCACHED_CLUSTER is in use.
Acceptance Criteria
Research spike.
Design Consideration/Limitations
Try to capture the ARN in some way if possible but if not, other data - eg: host, port, etc - might be useable for building entity relationships
Dependencies
N/A
Additional context
Once the available data is better understood, we need to flesh out the details of additional work needed to get that into the agent and documented.
Description
Trying to reduce the entity relationship data gaps when APM applications use AWS services. Need to explore what entity relationship data can be captured and emitted from the agent when either
AWS_ELASTICACHE_REDIS_CLUSTER
orAWS_ELASTICACHE_MEMCACHED_CLUSTER
is in use.Acceptance Criteria
Research spike.
Design Consideration/Limitations
Try to capture the ARN in some way if possible but if not, other data - eg: host, port, etc - might be useable for building entity relationships
Dependencies
N/A
Additional context
Once the available data is better understood, we need to flesh out the details of additional work needed to get that into the agent and documented.