Investigate relationship data that can be emitted from apps that use AWS_MQ_BROKER with RabbitMQ

[kford-newrelic]

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 AWS_MQ_BROKER with RabbtMQ 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.

[workato-integration]

https://new-relic.atlassian.net/browse/NR-255321

[obenkenobi]

AWS MQ is both RabbitMQ and ActiveMQ compatible. Thus the following needs to be investigated:

Rabbit MQ:

• The RabbitMQ's AMQP client instrumentation (of which we already instrument)

Active MQ:

• JMS

Doc for using JMS with Active MQ in AWS as it describes possible clients for ActiveMQ: https://docs.aws.amazon.com/amazon-mq/latest/developer-guide/amazon-mq-working-java-example.html

We might need to do the same with RabbitMQ with JMS.

[obenkenobi]

Link to the Active MQ Ticket for AWS MQ