AWS Kinesis¶
Use the script package series of "Guance Cloud Sync" 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 - Hosted Func: All prerequisites are automatically installed. Please continue with script installation.
If you deploy Func on your own, refer to Self-hosted Func
Install Script¶
Note: Please prepare a qualified Amazon AK in advance (for simplicity, you can directly grant global read-only permission
ReadOnlyAccess
)
Enable Hosted Script¶
- Log in to the 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 you have already configured cloud account information, skip this step.
- Click 【Test】, after the test succeeds, click 【Save】. If the test fails, 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 Kinesis
, click the 【Install】 button, and install it from the pop-up installation interface.
Manually Enable Script¶
- Log in to the Func console, click 【Script Market】, go to the official script market, search for:
guance_aws_kinesis
- After clicking 【Install】, input the corresponding parameters: AWS AK ID, AK Secret, and account name.
- Click 【Deploy Startup Script】, the system will automatically create a
Startup
script set and configure the corresponding startup script automatically. - After enabling, you can see the corresponding automatic trigger configuration in the 「Management / Automatic Trigger Configuration」. Click 【Execute】 to run immediately without waiting for the scheduled time. After a short while, you can view the execution task records and corresponding logs.
Verification¶
- In 「Management / Automatic Trigger Configuration」, confirm whether the corresponding task has an automatic trigger configuration, and at the same time, you can check the corresponding task records and logs for any anomalies.
- In Guance, under 「Infrastructure / Custom」, check if there is any asset information.
- In Guance, under 「Metrics」, check if there is any corresponding monitoring data.
Metrics¶
After configuring Amazon-CloudWatch, the default metric set is as follows. You can collect more metrics through configuration. Amazon CloudWatch Metric Details
Instance Metrics¶
The AWS/Kinesis
namespace includes the following instance metrics.
Metric | Description |
---|---|
IncomingBytes |
The number of bytes successfully placed into the Kinesis stream during the specified period. This metric includes bytes from PutRecord and PutRecords . Statistics Minimum, Maximum, and Average represent the number of bytes in a single put operation within the specified period. Shard-level metric name: IncomingBytes. Dimensions: StreamName. Units: Bytes |
IncomingRecords |
The number of records successfully placed into the Kinesis stream during the specified period. This metric includes records from PutRecord and PutRecords . Statistics Minimum, Maximum, and Average represent the number of records in a single put operation within the specified period. Shard-level metric name: IncomingRecords. Dimensions: StreamName. Units: Count |
WriteProvisionedThroughputExceeded |
The number of records rejected due to stream limits during the specified period. This metric includes limits from PutRecord and PutRecords operations. The most commonly used statistic for this metric is Average. When the Minimum statistic value is not zero, the stream's records will be limited within the specified period. When the Maximum statistic value is 0 (zero), no records in the stream will be limited within the specified period. Shard-level metric name: WriteProvisionedThroughputExceeded. Dimensions: StreamName. Units: Count |
PutRecords.Bytes |
The number of bytes placed into the Kinesis stream using PutRecords during the specified time period. Dimensions: StreamName. Units: Bytes |
PutRecords.Success |
The number of PutRecords operations measured per Kinesis stream where at least one record succeeded during the specified period. Dimensions: StreamName. Units: Count |
PutRecords.Latency |
The time measured for each PutRecords operation during the specified period. Dimensions: StreamName. Units: Milliseconds |
PutRecords.FailedRecords |
The number of records rejected due to internal failures. Measured for each PutRecords operation on every Kinesis data stream during the specified period. Occasional internal failures should be retried. Dimensions: StreamName. Units: Count |
PutRecords.ThrottledRecords |
The number of records rejected due to throttling limits. Measured for each PutRecords operation on every Kinesis data stream during the specified period. Dimensions: StreamName. Units: Count |
PutRecords.TotalRecords |
The total number of records measured for each PutRecords operation on every Kinesis data stream during the specified period. Dimensions: StreamName. Units: Count |
Objects¶
The collected AWS Kinesis object data structure can be viewed in 「Infrastructure - Custom」
{
"measurement": "aws_kinesis",
"tags": {
"class" : "aws_kinesis",
"cloud_provider" : "aws",
"create_time" : "2023/08/07 14:29:19",
"date" : "2023/08/07 14:29:19",
"date_ns" :"0",
"EncryptionType" :"NONE",
"HasMoreShards" :"false",
"name" :"zsh_test",
"RegionId" :"cn-northwest-1",
"RetentionPeriodHours":"24",
"StreamARN":"arn:aws-cn:kinesis:cn-northwest-1:294654068288:stream/zsh_test",
"StreamName":"zsh_test",
"StreamStatus":"ACTIVE"
}
}
Note: Fields in
tags
may change with subsequent updates.Tip 1: The
name
value is the instance name, used for unique identification. ```