AWS EC2¶

Use script market "TrueWatch cloud sync" series script packages to synchronize cloud monitoring and cloud asset data to TrueWatch

Configuration¶

Install Func¶

It is recommended to enable TrueWatch integration - extension - DataFlux Func (Automata): all prerequisites will be automatically installed, please continue with the script installation.

If you deploy Func yourself, refer to Self-deployed Func

Install Script¶

Note: Please prepare the required Amazon AK in advance (for simplicity, you can directly grant global read-only permission ReadOnlyAccess)

To synchronize EC2 cloud resource monitoring data, we install the corresponding collection script: "TrueWatch Integration (AWS EC2 Collection)" (ID: truewatch_aws_ec2)

After clicking [Install], enter the corresponding parameters: Amazon AK, Amazon account name.

Click [Deploy Startup Script], and the system will automatically create a Startup script set and automatically configure the corresponding startup script.

In addition, you can see the corresponding automatic trigger configuration in "Manage / Automatic Trigger Configuration". Click [Execute] to immediately execute once without waiting for the scheduled time. After a while, you can check the execution task records and corresponding logs.

We default to collecting some configurations, for details see Metrics section Customize Cloud Object Metrics

Verification¶

1. In "Manage / Automatic Trigger Configuration", confirm whether the corresponding task has the corresponding automatic trigger configuration, and at the same time, you can view the corresponding task records and logs to check for any abnormalities.
2. On the TrueWatch platform, in "Infrastructure / Custom", check if there are any asset information.
3. On the TrueWatch platform, in "Metrics", check if there are any corresponding monitoring data.

Metrics¶

After configuring Amazon CloudWatch, the default metric sets are as follows, more metrics can be collected through configuration Amazon CloudWatch Metric Details

Note: If memory or disk does not report metrics, go to the aws console to manually enable collection.

Instance Metrics¶

The AWS/EC2 namespace includes the following instance metrics.

CPU Metrics¶

The AWS/EC2 namespace includes the following CPU credit metrics for burstable performance instances.

Status Check Metrics¶

The AWS/EC2 namespace includes the following status check metrics. By default, status check metrics are available for free at a frequency of one minute. For newly launched instances, status check metric data is only available after the instance completes initialization (within a few minutes of the instance entering the running state). For more information about EC2 status checks, see Instance Status Checks. | Metrics | Description | | :--------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | StatusCheckFailed | Reports whether the instance passed both the instance status check and the system status check in the previous minute. This metric can be 0 (passed) or 1 (failed). By default, this metric is available for free at a frequency of one minute. Unit: Count | | StatusCheckFailed_Instance | Reports whether the instance passed the instance status check in the previous minute. This metric can be 0 (passed) or 1 (failed). By default, this metric is available for free at a frequency of one minute. Unit: Count | | StatusCheckFailed_System | Reports whether the instance passed the system status check in the previous minute. This metric can be 0 (passed) or 1 (failed). By default, this metric is available for free at a frequency of one minute. Unit: Count |

Objects¶

The structure of the AWS EC2 object data collected can be viewed in the "Infrastructure - Custom" section.

{
  "measurement": "aws_ec2",
  "tags": {
    "name": "i-0d7620xxxxxxx",
    "InstanceId": "i-0d7620xxxxxxx",
    "InstanceType": "c6g.xlarge",
    "PlatformDetails": "Linux/UNIX",
    "RegionId": "cn-northwest-1",
    "InstanceName": "test",
    "State": "running",
    "StateReason_Code": "Client.UserInitiatedHibernate",
    "AvailabilityZone": "cn-northwest-1"
  },
  "fields": {
    "BlockDeviceMappings": "{Device JSON data}",
    "LaunchTime": "2021-10-26T07:00:44Z",
    "NetworkInterfaces": "{Network JSON data}",
    "Placement": "{Availability Zone JSON data}",
    "message": "{Instance JSON data}"
  }
}

Note: Fields in tags, fields may change with subsequent updates.

Tip 1: The value of tags.name is the instance ID, used as a unique identifier. Tip 2: fields.message, fields.NetworkInterfaces, fields.BlockDeviceMappings are serialized JSON strings.