Mackerel supports obtaining and monitoring Amazon Elastic Compute Cloud (Amazon EC2) metrics in AWS Integration. When integrating with AWS Integration, billable targets are determined using the conversion 1 Instance = 1 Standard Host. AWS integration and mackerel-agent can also be used together. In such a case, system metrics and custom metrics will be integrated as one host (no duplicate charges will be made).
Please refer to the following page for AWS Integration configuration methods and a list of supported AWS services.
AWS Integration
Obtaining metrics
The metrics obtainable with AWS Integration’s EC2 support are as follows. For Metric explanations, refer to the AWS help page.
The maximum number of metrics obtainable is 21.
| Graph name | Metric | Metric name in Mackerel | Unit | Statistics |
|---|---|---|---|---|
| CPU | CPUUtilization | ec2.cpu.used | percentage | Average |
| CPU Credit | CPUCreditUsage CPUCreditBalance CPUSurplusCreditBalance CPUSurplusCreditsCharged |
ec2.cpu_credit.used ec2.cpu_credit.balance ec2.cpu_credit.surplus_balance ec2.cpu_credit.surplus_charged |
float | Average |
| Disk OPS | DiskReadOps DiskWriteOps |
ec2.disk_ops.read ec2.disk_ops.write |
float | Average |
| Disk IO | DiskReadBytes DiskWriteBytes |
ec2.disk_io.read ec2.disk_io.write |
bytes | Average |
| Network Traffic | NetworkIn NetworkOut |
ec2.network.in ec2.network.out |
bytes | Average |
| Network Packets | NetworkPacketsIn NetworkPacketsOut |
ec2.network_packets.in ec2.network_packets.out |
float | Average |
| Status Check Failed | StatusCheckFailed_Instance StatusCheckFailed_System StatusCheckFailed |
ec2.status_check_failed.instance ec2.status_check_failed.system ec2.status_check_failed.total |
float | Average |
| EBS Operation | EBSReadOps *1 EBSWriteOps *1 |
ec2.ebs_operation.read ec2.ebs_operation.write |
integer | Sum |
| EBS Bytes Used | EBSReadBytes *1 EBSWriteBytes *1 |
ec2.ebs_bytes_used.read ec2.ebs_bytes_used.write |
bytes | Sum |
| EBS Burst Bucket Balance | EBSIOBalance% *1 EBSByteBalance% *1 |
ec2.ebs_burst_bucket_balance.io ec2.ebs_burst_bucket_balance.throughput |
percentage | Average |
ediv id="ec2-nitro">*1 Occurs with Nitro-based instances. Click here for a list of instances.
Precautions
Among the graphs/metrics obtainable with AWS Integration, metrics included in the following graph are usually obtained in 5 minute intervals.
- CPU
- CPU Credit
- Disk OPS
- Disk IO
- Network Traffic
- Network Packets
- Status Check Failed
- EBS Operation
- EBS Bytes Used
- EBS Burst Bucket Balance
By enabling detailed monitoring, the metrics in the graph below will be obtained in 1-minute intervals.
- CPU
- Disk OPS
- Disk IO
- Network Traffic
- Status Check Failed
- EBS Operation
- EBS Bytes Used
This is specified by the AWS CloudWatch API.
Using with mackerel-agent
If mackerel-agent has already been installed on the target EC2 instance, host information from Mackerel will automatically be integrated and registered as one host. It will not be counted twice as a billable host.
If you prefer a more detailed style of monitoring with AWS Integration, we recommend installing mackerel-agent for EC2.
