Skip to content

AWS EKS

Collect AWS EKS cluster assets and AWS/EKS control plane monitoring data.

Configuration

Install Func

We recommend enabling Guance Integrations - Extensions - Hosted Func: all prerequisites are installed automatically. Continue with script installation.

To deploy Func yourself, see Self-hosted Func.

Enable the Script

Tip: Prepare suitable AWS access keys in advance (for simplicity, you can grant the global read-only permission ReadOnlyAccess).

Activate Script in DataFlux Func (Automata)

  1. Log in to the Guance console
  2. Click the 【Integration】 menu and select 【Cloud Account Management】
  3. Click 【Add Cloud Account】, select 【AWS】, and fill in the required information on the interface. If you have already configured the cloud account information before, ignore this step
  4. Click 【Test】, and 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 【Cloud Account Management】, and you can see the added cloud account in the list. Click the corresponding cloud account to enter the details page
  6. Click the 【Integration】 button on the cloud account details page, find AWS EKS under the Not Installed list, click the 【Install】 button, and the installation interface will pop up for installation.

Activate Script Manually

  1. Log in to the Func console, click [Script Market] to open the Guance script market, and search for integration_aws_eks.
  2. Click [Install], then enter the required parameters: AWS AK ID, AK Secret, and account name.
  3. Click [Deploy Startup Script]. The system automatically creates the Startup script set and configures the corresponding startup script.
  4. Once enabled, the corresponding automatic trigger configuration appears under [Management / Automatic Trigger Configuration]. Click [Execute] to run it immediately without waiting for the scheduled time. After a short wait, check the task execution records and logs.

Verification

  1. Under [Management / Automatic Trigger Configuration], confirm that an automatic trigger configuration exists for the task, and check the task records and logs for errors.
  2. In Guance, check [Infrastructure / Custom] for asset information.
  3. In Guance, check [Metrics] for the corresponding monitoring data.

Metrics

The measurement is aws_eks.

AWS EKS Metrics Reference

MetricName MetricDescribe Dimensions Unit
apiserver_admission_webhook_rejection_count_ADMIT Admission webhook rejection count (admit) ClusterName count
apiserver_admission_webhook_rejection_count_VALIDATING Admission webhook rejection count (validating) ClusterName count
apiserver_admission_webhook_request_total Total admission webhook requests ClusterName count
apiserver_admission_webhook_request_total_ADMIT Total admission webhook requests (admit) ClusterName count
apiserver_admission_webhook_request_total_VALIDATING Total admission webhook requests (validating) ClusterName count
apiserver_current_inflight_requests_MUTATING Current concurrent API Server requests (mutating) ClusterName count
apiserver_current_inflight_requests_READONLY Current concurrent API Server requests (readonly) ClusterName count
apiserver_flowcontrol_current_executing_seats Currently executing seats in API Priority and Fairness ClusterName count
apiserver_request_duration_seconds_DELETE_P99 Native P99 latency of DELETE requests ClusterName s
apiserver_request_duration_seconds_GET_P99 Native P99 latency of GET requests ClusterName s
apiserver_request_duration_seconds_LIST_P99 Native P99 latency of LIST requests ClusterName s
apiserver_request_duration_seconds_PATCH_P99 Native P99 latency of PATCH requests ClusterName s
apiserver_request_duration_seconds_POST_P99 Native P99 latency of POST requests ClusterName s
apiserver_request_duration_seconds_PUT_P99 Native P99 latency of PUT requests ClusterName s
apiserver_request_total API Server request count ClusterName count
apiserver_request_total_429 API Server request count (429) ClusterName count
apiserver_request_total_4XX API Server request count (4XX) ClusterName count
apiserver_request_total_5XX API Server request count (5XX) ClusterName count
apiserver_storage_size_bytes Disk space allocated by etcd ClusterName B
etcd_mvcc_db_total_size_in_use_in_bytes Database size actually used by etcd ClusterName B
scheduler_pending_pods Pods pending in the scheduler ClusterName count
scheduler_pending_pods_ACTIVEQ Pods pending in the scheduler (activeq) ClusterName count
scheduler_pending_pods_BACKOFF Pods pending in the scheduler (backoff) ClusterName count
scheduler_pending_pods_GATED Pods pending in the scheduler (gated) ClusterName count
scheduler_pending_pods_UNSCHEDULABLE Pods pending in the scheduler (unschedulable) ClusterName count
scheduler_schedule_attempts_ERROR Scheduling attempts (error) ClusterName count
scheduler_schedule_attempts_SCHEDULED Scheduling attempts (scheduled) ClusterName count
scheduler_schedule_attempts_total Scheduling attempts (total) ClusterName count
scheduler_schedule_attempts_UNSCHEDULABLE Scheduling attempts (unschedulable) ClusterName count

Feedback

Is this page helpful?