We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
receiver/rabbitmq
I use Datadog and AmazonMQ and I flow RabbitMQ metrics to my ecosystem.
The challenge I had is that there is a limit of 500 queues that CloudWatch can monitor. As an alternative for this, I found this receiver.
Although this works for queue metrics there are some metrics that flow from Datadog that don't exist in this receiver.
I would like to see the following metrics coming from this receiver:
aws.amazonmq.rabbit_mqdisk_free
aws.amazonmq.rabbit_mqfd_used
aws.amazonmq.rabbit_mqmem_limit
aws.amazonmq.rabbit_mqmem_used
It seems we should be able to fetch these from node metrics in the /api/nodes endpoint.
/api/nodes
Reference
N/A
The text was updated successfully, but these errors were encountered:
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Sorry, something went wrong.
No branches or pull requests
Component(s)
receiver/rabbitmq
Is your feature request related to a problem? Please describe.
I use Datadog and AmazonMQ and I flow RabbitMQ metrics to my ecosystem.
The challenge I had is that there is a limit of 500 queues that CloudWatch can monitor. As an alternative for this, I found this receiver.
Although this works for queue metrics there are some metrics that flow from Datadog that don't exist in this receiver.
Describe the solution you'd like
I would like to see the following metrics coming from this receiver:
aws.amazonmq.rabbit_mqdisk_free
aws.amazonmq.rabbit_mqfd_used
aws.amazonmq.rabbit_mqmem_limit
aws.amazonmq.rabbit_mqmem_used
It seems we should be able to fetch these from node metrics in the
/api/nodes
endpoint.Reference
Describe alternatives you've considered
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: