keptn Keptn Tutorials, 19 Mar 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Tutorial - Keptn Quality Gates for Dynatrace on K3s

Description

Follow the tutorial yourself: https://tutorials.keptn.sh/tutorials/keptn-quality-gates-dynatrace-08-on-k3s/index.html?index=..%2F..keptn08x#0

If you have tools that deploy your applications and then run tests against those you have done the hard work already. Keptn's Quality Gates help you to automate the evaluation of your test results and the monitoring data captured during your tests. Keptn does this by embracing the concept of Service Level Indicators (SLIs) and Service Level Objectives (SLOs). Essentially SLIs are metrics such as Response Time, Throughput, Error Rate, Number of Database Calls, Time spent in external service calls, ... and SLOs define which objective you have for these SLIs to consider your service to be adhering to what you expect, e.g: Response Time of Login should be faster than 200ms or Login should not make more than 1 database query.
Keptn didn't come up with these concepts. They have been around for a while and made very popular thanks to the work that Google did around Site Reliability Engineering

In this tutorial we teach you how you can use Keptn Quality Gates to automatically analyze important metrics (SLIs) that Dynatrace captures while your system is under load, e.g: during a load test and compare them against your expected behavior (SLOs). This comparison can either be against well defined thresholds, e.g: 200ms response time but can also be a comparison against previous test results, e.g: response time should not get slower than 10% of our previous build.

All tutorials: https://tutorials.keptn.sh
Website: https://keptn.sh
Slack: https://slack.keptn.sh

A

Hey captain community, I'm andy grabner and I just finished a tutorial captain quality gates with dynatrace using k3s, and I thought I want to walk through the installation steps with you to really show you how easy this is because I know a lot of you are interested in quality gates, so quality gates is really all about automating, the extraction of data from a monitoring tool like dynatrace and instead of you looking at dashboards and analyzing the data kit, and can do this for you now. What I've done is.

A

I just walked through the tutorial here installing of captain k3s. I have a linux machine, I'm running on ec2, so this is my ssh, my shell, I'm here everything is clean. Nothing is going on. What else do I have here? um I have already created particular things that I need. Like a dynatrace token, I have an api token. I have also created a pass token.

A

So in case you don't know how this works in dynatrace, you can go to uh settings integration, dynatrace api, and then you just create a token based on the prerequisites that I've put into the tutorial same is true. For the pass token, the pass token is needed for installing the one agent, because my installation scripts also automatically put an agent on your k3s, so we can fully monitor it and other than that. What else I need is my dynatrace tenant url.

A

If you have managed it would be your managed url, slash e, slash environment id, and that's really all I need now, let's go back. What do I need to do? First, on my linux machine, I need to take this and I need to install a bunch of tools like git, like curl, jq, 3 and also yq.

A

This is all this should still be empty here, all good. Now. The next thing I need to clone my git repo that contains actually all of my samples, that's the captain on k3s in the captain sandbox.

A

So I'm just doing this and then check out the latest branch, which means we're all good, and we actually have this installation script here now. The next thing I need to do is: I need to export all these variables now. I've prepared this. So let me walk over to here now. Remember these tokens are all temporarily, so I will delete them, but important is that oops, uh I'm just posting them in here um token and tenant is clear: the owner email, that's my email, my username in my dyna choice, environment.

A

The reason why this is important is because we are creating some dashboards laid on automatically and we're using that email. It's the username that creates the dashboard and I'm also using let's encrypt, to generate an ssl certificate and because this is just a temporary one on a on a domain name. That is very temporary. I'm just specifying that. Okay next thing is in my tutorial. I give different installation options. I use the first one. This is just installing captain the control plane, so I'm posting this in this will run for a little bit.

A

It will install k3s. It will then install captain on it. It will install gt, it will install all the different components. You know it's creating uh certificates and and all that stuff. So, while this is running, let me just put pause here, because this will take about five minutes depending on how fast, especially the certificate stuff is. um So let me pause here and I'll come back in a second all right, I am back. I think it was about five minutes, and you can see that my captain is now fully installed.

A

So the end of my installation, script really says explore more there's a lot of text here. That gives me overview of what is actually has been installed, how I can access captain- and this is actually what I want to focus on as well, but just as a reminder, this is also all documented here in installation.

A

This is the output of the script. That tells you how you can access your captain, your bridge, your api token, also I'm installing gt as a git service and also for the individual use cases like, particularly for the quality git use case, how we can get started. But let me show you quickly by following my links: what has been installed most important is: I can get to the captain's bridge.

A

This is the bridge here. Yes, it is uses a certificate, but it's self-signed. uh So that's why you can safely go over this. If you obviously use this in production, you would create your own certificates. Now the username by default is captain.

A

The password of the bridge will also be shown here sign in and let's see, if this works, then I should see captain in a second now one thing that you will see here: the ip address uses accepted io, so we're just using this dns feature to have a dns name on your ip address, so that doesn't mean that anybody can go to you to your site if this is an internal ip. This is just something where we can then use sub domains easily, because now you can see all of my projects.

A

The project relevant for this tutorial is the dynatrace project, but let me also immediately open up gitti, because I think this is very important, so I've defined an upstream git into a self-hosted git environment. Here this is where you can see the shipyard file that was used right. I can zoom in this is great.

A

You can also see the dynatrace con file, for instance that is used and because this is a single stage, shipyard file with the quality gate stage here- and here are additional things like hey there is I'm using monaco monitoring as code to automatically create dashboards, so this is a great way to explore, also and modify the files. Now, let's go back to captain. I have my dynatrace project here. This is where I have the quality gate stage.

A

Let's click on services, the default one that was created was the demo service because remember we wanted to get you quick up and running and after the installation, a quality gate was immediately triggered. That means you already see a quality gate result with a couple of metrics also with the individual values. Now you may wonder: where do these metrics all come from?

A

Well, if you click on the little bar here, you get to see the heat map in full screen and you also get a dashboard link because remember what also happened as part of delivery as part of the quality gate, I'm using monaco monaco means monitoring is code. As part of my demo, this dashboard was fully automatically created, meaning these are metrics that you hopefully have on your dynamics environment anyway.

A

As soon as you have one service monitored, this dashboard should show some value, and I just came up with some default thresholds, doesn't mean that this is exactly what works for you, but to show you that every time you run the quality gate, this dashboard will be analyzed now talking about running another quality gate.

A

If I go back to my terminal window here, then, under the first section here, the quality get used, because it tells me how I can trigger a new quality gate, and I'm just doing this to the captain. Cli captain trigger evaluation, so captain trigger evaluation for this project. For this stage and uh for this uh service here we go it triggers it. Captain is an event-driven system. This was my request to trigger a new quality gate.

A

I also get the token back, so I can also use now the api or the cli to ask when it's finished. I can do a lot of things, a lot of great things. I can also go back now to my dynatrace project services. Demo.

A

Now I see my second quality gate being evaluated all right now, there's more you can do with this, but I thought I want to show you how fast you can install captain. You can get it up and running, there's also more use cases. As you can see here, remediation performance delivery advanced. I will create more tutorials, but hopefully this shows you that this is really. You know super easy. Okay, thank you. So much uh talk to you soon. Bye.