Difficulty: medium
Estimated Time: 30 minutes

In this scenario we will deploy an example microservice voting app in Kubernetes that issues votes for your favourite: dogs or cats. Results are stored in a database and then a report can be generated with the results.

Suddenly there are more people voting using our application and the app becomes slower and slower. In this lab we will find the microservices bottleneck and check how we can scale this application to handle the required load.

Competencies required

The student needs to understand the basic concepts of microservices applications, containers and Kubernetes, and be able to check the status of deployed Kubernetes resources (pods, deployments, services) and nodes.


  • Explore a microservices application using Sysdig Monitor:
    • Where is each container running?
    • How does this microservices application work?
    • Which services talk to each other?
    • What's running inside each container and microservice?
  • Monitor a web services application. Key metrics and monitoring approaches: Golden signals, Utilization Saturation and Errors (USE) resource monitoring and Kubernetes orchestration.
  • Identify performance bottlenecks in the application.
  • Scale the application to handle the required load while monitoring the changes.
  • Tailor Sysdig to provide application assurance for this microservices application
    • Custom dashboards
    • Useful alerts on health metrics

Conclusions and takeaways

During this lab we have seen how Sysdig Monitor provides deep visibility into your containerized infrastructure and out of the box allows to:

  • Explore the containerized infrastructure and a microservices application.
  • Monitor a web services application using key metrics and monitoring approaches:
    • Golden signals and application metrics monitoring
    • USE resource and container limits monitoring
    • Kubernetes orchestration and kube-state-metrics monitoring
  • Identify performance bottlenecks in the application, in this case a CPU bottleneck
  • Confirm that scaling the application can handle the required load

Sysdig Monitor Lab 01: Application performance analysis

Step 1 of 7

Setting up the environment

We have set up a Kubernetes cluster just for you. On the right you can see the terminal of the master node, from which you can interact with the cluster using the kubectl tool, which is already configured.

For instance, you can get the details of the cluster by executing
kubectl cluster-info

You can view the nodes in the cluster with the command
kubectl get nodes

You should see 2 nodes: one master and a worker.

Check that you are admin:
kubectl auth can-i create node

In order to follow this course, you will need a Sysdig Monitor account, with Administrator access privileges.

Log in the Sysdig Monitor web UI, go to your profile Settings, and in the Agent Installation tab you will find your Access Key (something like 5ca1ab1e-d3ad-beef-dea1-deba7ab1ed0c). Keep it handy, as you will need it to authorize the agent against the backend.

Agent key