CloudWatch V3

This integration exports Prometheus metrics from your CloudAMQP cluster to CloudWatch, delivered via our OpenTelemetry Collector.

Authentication

This integration uses AssumeRole to authenticate with CloudWatch.

To set up the integration you need to create a role in your CloudWatch account. This role should have these permissions:

• logs:PutLogEvents

• logs:CreateLogStream

• logs:CreateLogGroup

Example JSON config:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "VisualEditor0",
      "Effect": "Allow",
      "Action": [
        "logs:PutLogEvents",
        "logs:CreateLogStream",
        "logs:CreateLogGroup"
      ],
     "Resource": "*"
    }
  ]
}

To allow CloudAMQP to assume that role in your account you need to setup a trusted entity for the newly created role.

In that you specify which account and user is allowed to assume the role. We also make use of ExternalID which allows you to see a connection between the role and the integration on CloudAMQP. For all integration we list the external id so you can see which integration uses which role if you have setup multiple. We autogenerate an external id when you create the integration but you can use any value for this. Here is an example config for a trusted entity

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "Statement1",
      "Effect": "Allow",
      "Principal": {
        "AWS": "arn:aws:iam::714915985929:user/cloudamqp-metrics-publisher"
      },
      "Action": "sts:AssumeRole",
      "Condition": {
        "StringEquals": {
          "sts:ExternalId": "cloudamqp-pxaqltthad"
        }
      }
    }
  ]
}

The principal used in this example is the real ARN that we use so you can copy and paste this and only adjust the external id to match the configuration for the integration you have setup.

All metrics are exported with the labels/tags instance and cluster, which are populated with the name of the server and cluster. You can also set custom tags when configuring the integration.

Exported server metrics

Exported LavinMQ metrics

Exported RabbitMQ metrics

Metrics Filtering

The metrics listed above are the metrics exported by default. However, you can use the metrics_filter endpoint to specify exactly which metrics you want to export. See the API documentation for more details.

The complete list of available metrics that can be included in the metrics filter includes:

• All metrics available from the server’s /metrics endpoint (broker metrics)
• All metrics available from the server’s /metrics/detailed endpoint (detailed broker metrics). Note: Detailed metrics can be resource-intensive on servers with many objects such as connections and queues.
• Server metrics:
  • system_cpu_utilization_ratio
  • system_disk_io_bytes_total
  • system_disk_operation_time_seconds_total
  • system_disk_operations_total
  • system_filesystem_usage_bytes
  • system_filesystem_utilization_ratio
  • system_memory_limit_bytes
  • system_memory_usage_bytes
  • system_linux_memory_available_bytes
  • system_network_io_bytes_total
  • system_paging_usage_bytes

Histograms and summaries are selected by their family name, for example rabbitmq_message_size_bytes for the RabbitMQ message size histogram. The collector merges the bucket, sum and count series into that single metric, so listing the family name exports all of them. The full list of names accepted by the filter for your instance is available from the valid_metrics endpoint.

← Back to Metrics Integrations