Skip to content

Latest commit

 

History

History
88 lines (61 loc) · 2.84 KB

README.md

File metadata and controls

88 lines (61 loc) · 2.84 KB
Raw

Testing Metricbeat

Create kubernetes cluster using kind

Follow instructions at https://kind.sigs.k8s.io/docs/user/quick-start/#installation and install kind.

Create a kind kubernetes cluster.

kind create cluster  --image 'kindest/node:v1.21.1'

Deploy Kube-state-metrics

Prerequisite for collecting kubernetes meaningful metrics is kube-state-metrics. Deploy it to your cluster manually by

git clone [email protected]:kubernetes/kube-state-metrics.git
cd kube-state-metrics/

kubectl apply -k .

Create ELK stack

You can spin up an ELK stack in two ways

  1. [Proposed] Using elastic cloud https://cloud.elastic.co
  2. Locally on your kind cluster (EK tuple will suffice).
# Deploy Elasticsearch and Kibana
cd metricbeat/module/kubernetes/_meta/test/docs
kubectl apply -f 01_playground/ek_stack.yaml

# Expose Kibana with port forwarding. In your browser visit localhost:5601
kubectl port-forward deployment/kibana 5601:5601

Playground Metricbeat Pod

A slightly modified (as of beats/deploy/kubernetes/metricbeat-kubernetes.yaml) all-in-one metricbeat manifest resides under 01_playground directory. The daemonset executes an infinite sleep command instead of starting metricbeat.

ELASTICSEARCH_HOST, ELASTICSEARCH_PORT, ELASTICSEARCH_USERNAME, ELASTICSEARCH_PASSWORD variables are set according to local kind EK stack.

In case of Elastic Cloud deployment configure the variables ELASTIC_CLOUD_ID and ELASTIC_CLOUD_AUTH properly.

Deploy metricbeat

kubectl apply -f 01_playground/metricbeat.yaml

Build and launch metricbeat process

Next step is to build metricbeat binary and copy it in the running metricbeat pod.

Under beats/metricbeat execute

# Build metricbeat
GOOS=linux GOARCH=amd64 go build

# Copy binary in pod
kubectl cp ./metricbeat `kubectl get pod -n kube-system -l k8s-app=metricbeat -o jsonpath='{.items[].metadata.name}'`:/usr/share/metricbeat/ -n kube-system

The above command only copies metricbeat binary. In case of configuration files updates it can be modified to copy also those files in the right container paths.

# Exec in the container and launch metricbeat
kubectl exec `kubectl get pod -n kube-system -l k8s-app=metricbeat -o jsonpath='{.items[].metadata.name}'` -n kube-system -- bash -c "metricbeat -e -c /etc/metricbeat.yml"

Metricbeat will launch and the process logs will appear in the terminal.

You can as well exec in metricbeat pod with bash command and then run metricbeat. This gives the flexibility to easily start and stop the process.

Test Iterations

In case a new update is needed in the binary or configurations files

  1. delete the running metricbeat pod.
# Delete metricbeat
kubectl delete pod `kubectl get pod -n kube-system -l k8s-app=metricbeat -o jsonpath='{.items[].metadata.name}'`
  1. Execute previous step (Build and launch metricbeat process)