Getting started with sumologic for AWS EKS mertics and alarms
Tags: eks, sumologic, observability, aws
Published: 2022-10-01 18:54:41


We will start with Sumologic’s integration with Amazon EKS: 
Monitor the health of clusters, pod, and alarm configuration and testing.

Amazon Elastic Kubernetes Service (EKS) one of the leading kubernetes cluster for deployment, scaling, and management of containerized applications. With Sumo Logic you can monitor and troubleshoot container health, replication, load balancing, pod state, and hardware resource allocation with ease.

Pre-requisite for this guide
i)Access to an AWS account.
ii)A running EKS cluster
iii)Sumlogic 30day's trial account

Signup for 30days free trial 
https://www.sumologic.com/sign-up

![sumologic trial](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/e2nqyke4wj7vi2pm4ovq.png)

Once you login in Sumologic's trial account, go to app catalog

![Sumologic trial login](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/b1dzdfztn6cn6yg4lky1.png)

Next, select Kubernetes, it will show two option to integrate one with helm and other with kubectl apply with the GitHub repo files.


![options for app integration](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/m8sso02mrvpaefoscgs0.png)

I've opted for 2nd option for better visibility, once the setup done, you can see pods are running for Sumologic and you will see one pods as completed as this is used for setup job.


![kubectl get po](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/283fomazpbezcew238ja.png)

Once the setup completed you can go to next section and now you can explore the dashboard.

You will get four different view of clusters 
i)nodes

![nodeview](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/gu4bmp3ak3h7wzu0491b.png)

ii) namespace
![namespace view](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/a4ht42lb046vtntu4wlw.png)

iii)deployments

![deployment view](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/hu8pcweib386003eq4l3.png)
iv)services

![service view](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/qrw2m8v0g6jnybmvxkua.png)

Next we have deployed one service, which we will test for alert testing

![kubectl get deploy](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/9gitpigktiufxnj8bm1h.png)

We will configure and use stress for load test to hit the CPU alarms in one of the app pod.

![Stress](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/aa4k62lzt21qnn7o0axf.png)

We will get alert in email during higher CPU utilization
![Alert notification](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/flz4jvadgykdcfiry1n6.png)
Also we will get resolve status in email during CPU utilization is normal

![resolved notification](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/t0xuf5192z2hi3x8zhql.png)

For configuration of alarms you need select configure monitor from the drop down show in the snapshots

![configure alarms](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/z2oq6j50s6yhn1o30re8.png)


![node cpu warning](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/3tqn3ekttxzer3e63abe.png)


That's all for now, will publish more on sumologic and kubernetes soon.