You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| stats min(pod_number_of_containers) as requested, min(pod_number_of_running_containers) as running, ceil(avg(pod_number_of_containers-pod_number_of_running_containers)) as pods_missing by kubernetes.pod_name
-**Important Note:** Anything above 4% of CPU it will send a notification email, ideally it should 80% or 90% CPU but we are giving 4% CPU just for load simulation testing
138
+
-**Configure Actions**
139
+
-**Create New Topic:** eks-alerts
140
+
-**Email:**dkalyanreddy@gmail.com
141
+
- Click on **Create Topic**
142
+
-**Important Note:**** Complete Email subscription sent to your email id.
143
+
-**Add name and description**
144
+
-**Name:** EKS-Nodes-CPU-Alert
145
+
-**Descritption:** EKS Nodes CPU alert notification
146
+
- Click Next
147
+
-**Preview**
148
+
- Preview and Create Alarm
149
+
-**Add Alarm to our custom Dashboard**
150
+
- Generate Load & Verify Alarm
151
+
```
152
+
# Generate Load
153
+
kubectl run --generator=run-pod/v1 apache-bench -i --tty --rm --image=httpd -- ab -n 500000 -c 1000 http://sample-nginx-service.default.svc.cluster.local/
154
+
```
68
155
69
-
## Step-09: Clean-Up Container Insights
156
+
## Step-10: Clean-Up Container Insights
70
157
```
71
158
# Template
72
159
curl https://raw.githubusercontent.com/aws-samples/amazon-cloudwatch-container-insights/latest/k8s-deployment-manifest-templates/deployment-mode/daemonset/container-insights-monitoring/quickstart/cwagent-fluentd-quickstart.yaml | sed "s/{{cluster_name}}/cluster-name/;s/{{region_name}}/cluster-region/" | kubectl delete -f -
0 commit comments