Skip to content

AWS ElastiCache Serverless

Use the "Guance Cloud Sync" series of script packages in the script market to sync cloud monitoring and cloud asset data to Guance

Configuration

Install Func

It is recommended to activate the Guance integration - extension - DataFlux Func (Automata): all prerequisites are automatically installed, please proceed with the script installation.

If deploying Func manually, refer to Manual Func Deployment

Install Script

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

Automata Version Activation Script

  1. Log in to the Guance console
  2. Click on the 【Integration】 menu, select 【Cloud Account Management】
  3. Click 【Add Cloud Account】, select 【AWS】, and fill in the required information on the interface. If the cloud account information has been configured before, ignore this step
  4. Click 【Test】, if the test is successful, click 【Save】. If the test fails, please check if the relevant configuration information is correct and test again
  5. Click on the 【Cloud Account Management】 list to see the added cloud account, click on the corresponding cloud account to enter the details page
  6. Click the 【Integration】 button on the cloud account details page, find AWS ElastiCache Serverless under the Not Installed list, click the 【Install】 button, and the installation interface will pop up for installation.

Manual Activation Script

  1. Log in to the Func console, click on the 【Script Market】, enter the Guance script market, and search for integration_aws_elasticache_serverless

  2. Click 【Install】, then enter the corresponding parameters: AWS AK ID, AK Secret, and account name.

  3. Click 【Deploy Startup Script】, the system will automatically create the Startup script set and configure the corresponding startup script.

  4. After activation, 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.

Verification

  1. In 「Manage / Automatic Trigger Configuration」, confirm whether the corresponding task has the corresponding automatic trigger configuration, and you can also check the corresponding task records and logs to see if there are any exceptions
  2. In Guance, check if the asset information exists in 「Infrastructure / Custom」
  3. In Guance, check if there is corresponding monitoring data in 「Metrics」

Metrics

After configuring Amazon CloudWatch, the default Measurement is as follows, more metrics can be collected through configuration Amazon CloudWatch Metrics Details

Serverless Cache Metrics

Metric Description Unit
BytesUsedForCache Total number of bytes used by data stored in the cache. Bytes
ElastiCacheProcessingUnits Total number of lastiCacheProcessingUnits (ECPU) consumed to execute requests on the cache Count
SuccessfulReadRequestLatency Latency of successful read requests. Microseconds
SuccessfulWriteRequestLatency Latency of successful write requests Microseconds
TotalCmdsCount Total number of all commands executed in the cache Count
CacheHitRate Represents the cache hit rate. This is calculated using cache_hits and cache_misses statistics as follows: cache_hits /(cache_hits + cache_misses). Percentage
CacheHits Number of successful read-only key lookups in the cache. Count
CurrConnections Number of client connections to the cache. Count
ThrottledCmds Number of requests throttled by ElastiCache because the workload scaled faster than ElastiCache could scale. Count
NewConnections Total number of connections accepted by the server during this period. Count
CurrItems Number of items in the cache. Count
CurrVolatileItems Number of items in the cache with TTL. Count
NetworkBytesIn Total number of bytes transmitted to the cache Bytes
NetworkBytesOut Total number of bytes transmitted from the cache Bytes
IamAuthenticationExpirations Total number of expired IAM authenticated Redis connections. You can find more information about IAM authentication in the user guide. Count
IamAuthenticationThrottling Total number of throttled IAM authenticated Redis AUTH or HELLO requests. You can find more information about IAM authentication in the user guide. Count
KeyAuthorizationFailures Number of failed attempts by users to access keys they do not have permission to access. We recommend setting an alarm for this to detect unauthorized access attempts. Count
AuthenticationFailures Total number of failed attempts to authenticate to Redis using the AUTH command. We recommend setting an alarm for this to detect unauthorized access attempts. Count
CommandAuthorizationFailures Number of failed attempts by users to run commands they do not have permission to invoke. We recommend setting an alarm for this to detect unauthorized access attempts. Count

Objects

The collected Amazon AWS ElastiCache Serverless object data structure can be seen in 「Infrastructure - Custom」

{
    "category": "custom_object",
    "fields": {
      "CreateTime": "2024-04-10T02:45:41.921000Z",
      "DailySnapshotTime": "00:00",
      "Description": " ",
      "Endpoint": "{\"Address\": \"test-es-serverless-xxxx.serverless.cnw1.cache.amazonaws.com.cn\", \"Port\": 6379}",
      "ReaderEndpoint": "{\"Address\": \"test-es-serverless-xxxx.serverless.cnw1.cache.amazonaws.com.cn\", \"Port\": 6380}",
      "SecurityGroupIds": "[\"sg-099fc30041cxxxx\"]",
      "SubnetIds": "",
      "message": {}
    },
    "measurement": "aws_elasticache",
    "tags": {
      "ARN": "arn:aws-cn:elasticache:cn-northwest-1:xxxxx:serverlesscache:test-es-serverless",
      "Engine": "redis",
      "FullEngineVersion": "7.1",
      "MajorEngineVersion": "7",
      "RegionId": "cn-northwest-1",
      "ServerlessCacheName": "test-es-serverless",
      "Status": "available",
      "name": "test-es-serverless"
    }
  }

Note: The fields in tags and fields may change with subsequent updates

Tip 1: tags.name value is the instance ID, used as a unique identifier

Tip 2: fields.message, fields.network_interfaces, fields.blockdevicemappings are JSON serialized strings ```

Feedback

Is this page helpful? ×