Start your 14-day free trial today & Get 20% Off All Annual Managed ELK Plans

No Credit Card Required

Try Logit.io Free

Already have an account? Sign In

Send data via AWS Elastic Kubernetes Service to your Logstash instance provided by Logit.io

AWS Elastic Kubernetes Service

Ship AWS EKS Metrics to Logstash

Metricbeat is an open source shipping agent that lets you ship AWS Elastic Kubernetes Service (EKS) Metrics to one or more destinations, including Logstash.

Step 1 - PrerequisitesCopy

Firstly Make sure you have the aws cli, eksctl & kubectl installed on local machine using the following guide

Also make sure you have setup aws configure with your AWS credentials.

To do this run run the following command in your aws terminal.

aws configure

When you type this command, the AWS CLI prompts you for four pieces of information: access key, secret access key, AWS Region, and output format. This information is stored in a profile named default. This profile is used when you run commands, unless you specify another one.

Step 2 - Connecting to the clusterCopy

Update your config by running the following command. Replace <enter_region> and <enter_name> with your AWS cluster region and name.

aws eks --region <enter_region> update-kubeconfig --name <enter_name>

Check you can connect to your cluster by running the following command:

kubectl get svc

Step 3 - kube-state-metricsCopy

You will need an instance of kube-state-metrics running on your cluster before you install metricbeat.

Cloning the kube-state-metrics repository locally and applying the example is the easiest way to generate some metrics. You can tailor these to your needs at a later stage.

git clone https://github.com/kubernetes/kube-state-metrics.git

Change into the newly downloaded directory:

cd go/src/k8s.io/kube-state-metrics/

Then to deploy this project, you can simply run:

kubectl apply -f examples/standard
Metricbeat requires kube-state-metrics to be deployed and running to gather the cluster metrics. You can read more about kube state metrics on Github

Step 4 - Deploy MetricbeatCopy

You're going to need the metricbeat deployment manifest.

curl -L -O cdn.logit.io/metricbeat-kubernetes-7.10.0.yaml

Now you have the manifest we need to add your Stack Logstash endpoint details. Open the file in the terminal editor using the vim or nano command. Alternatively you can choose Open Editor from the console toolbar to make your changes.

vi metricbeat-kubernetes-7.10.0.yaml

or

nano metricbeat-kubernetes-7.10.0.yaml

Update the following lines in the yaml with your Stack Logstash endpoint and Beats-SSL port.

Note: The code snippet occurs two times in the yaml file and needs updating in both.
env:
- name: LOGSTASH_HOST
  value: "guid-ls.logit.io"
- name: BEATS_PORT
  value: "00000"

After updating the code should look as below.

env:
- name: LOGSTASH_HOST
  value: ["your-logstash-host"]
- name: BEATS_PORT
  value: ["your-ssl-port"]

Exit and save the file.

Step 5 - Apply your updatesCopy

Now we're going to apply the file to the cluster.

kubectl apply -f metricbeat-kubernetes-7.10.0.yaml
If you need to apply further updates after running the apply command you may need to remove the yaml file, make your changes and then apply again.

Step 6 - Confirm DeploymentCopy

Confirm your pod has deployed, you should see output similar to that below.

kubectl get po -A

or

kubectl logs ["podname"] --namespace=kube-system

Browse to Kibana and you should see Metrics arriving in your Stack.

Step 7 - how to diagnose no data in StackCopy

If you don't see data appearing in your Stack after following the steps, visit the Help Centre guide for steps to diagnose no data appearing in your Stack or Chat to support now.

Toggle View

Expand View

Return to Search