AWS KinesisAnalytics¶
Use the "Guance Cloud Sync" series script packages in the script market to synchronize cloud monitoring and cloud asset data to Guance.
Configuration¶
Install Func¶
It is recommended to enable Guance Integration - Extension - Managed Func: 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 an Amazon AK that meets the requirements in advance (for simplicity, you can directly grant global read-only permission
ReadOnlyAccess
)
Managed Version Activation Script¶
- Log in to Guance Console
- Click on the 【Integration】 menu, select 【Cloud Account Management】
- Click 【Add Cloud Account】, choose 【AWS】, fill in the required information on the interface; if the cloud account information has been configured before, skip this step
- Click 【Test】, after a successful test click 【Save】, if the test fails, please check whether the related configuration information is correct and retest
- In the 【Cloud Account Management】 list, you can see the added cloud accounts, click on the corresponding cloud account to enter the details page
- Click the 【Integration】 button on the cloud account details page. In the
Not Installed
list, findAWS KinesisAnalytics
, click the 【Install】 button, and install it from the pop-up installation interface.
Manual Activation Script¶
-
Log in to the Func Console, click 【Script Market】, enter the official script market, search for:
guance_aws_kinesis_analytics
-
After clicking 【Install】, input the corresponding parameters: AWS AK ID, AK Secret, and account name.
-
Click 【Deploy Start Script】, the system will automatically create a
Startup
script set and automatically configure the corresponding start scripts. -
After enabling, you can see the corresponding automatic trigger configuration in 「Management / Automatic Trigger Configuration」. Click 【Execute】, which will immediately execute once without waiting for the scheduled time. Wait for a moment, you can view the execution task records and corresponding logs.
Verification¶
- In 「Management / 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.
- In Guance, under 「Infrastructure / Custom」, check if there is asset information.
- In Guance, under 「Metrics」, check if there are corresponding monitoring data.
Metrics¶
After configuring Amazon-Cloud Monitoring, the default metric sets are as follows. You can collect more metrics through configuration. Amazon Cloud Monitoring Metric Details
Metric | Description | Unit |
---|---|---|
cpuUtilization |
The overall percentage of CPU utilization in the TaskManager. For example, if there are five TaskManagers, Kinesis Data Analytics will publish five samples of this metric at each reporting interval. | Percentage |
containerCPUUtilization |
The total percentage of CPU utilization in the TaskManager containers within the Flink application cluster. For example, if there are five TaskManagers, then correspondingly there are five TaskManager containers, and Kinesis Data Analytics publishes 2 * 5 samples of this metric every 1 minute report interval. | Percentage |
containerMemoryUtilization |
The overall percentage of memory utilization in the TaskManager containers within the Flink application cluster. For example, if there are five TaskManagers, then correspondingly there are five TaskManager containers, and Kinesis Data Analytics publishes 2 * 5 samples of this metric every 1 minute report interval. | Percentage |
containerDiskUtilization |
The overall percentage of disk utilization in the TaskManager containers within the Flink application cluster. For example, if there are five TaskManagers, then correspondingly there are five TaskManager containers, and Kinesis Data Analytics publishes 2 * 5 samples of this metric every 1 minute report interval. | Percentage |
heapMemoryUtilization |
The overall heap memory utilization of TaskManagers. For example, if there are five TaskManagers, Kinesis Data Analytics will publish five samples of this metric at each reporting interval. | Percentage |
oldGenerationGCCount |
The total number of old garbage collection operations that occurred across all TaskManagers. | Count |
oldGenerationGCTime |
The total time spent performing old garbage collection operations. | Milliseconds |
threadCount |
The total number of live threads used by the application. | Count |
Objects¶
The collected AWS KinesisAnalytics object data structure can be viewed in 「Infrastructure - Custom」
{
"measurement": "aws_kinesis_analytics",
"tags": {
"ApplicationARN": "arn:aws-cn:xxxx:xxxx",
"ApplicationMode": "STREAMING",
"ApplicationName": "zsh_test",
"ApplicationStatus": "RUNNING",
"ApplicationVersionId": "3",
"RegionId": "cn-northwest-1",
"RuntimeEnvironment": "FLINK-1_15",
"name": "zsh_test"
},
"fields": {
"message" : "{Instance JSON data}"
}
}
Note: Fields in
tags
andfields
may change with subsequent updates.