 Thank you, everyone, for joining this little detail today. I'm David Lorete. I work as an integration engineer at SISD. I want to show you how I monitor CSGO server with Prometheus. We describe it. We started this project because we wanted to describe how to monitor a full stack of monitoring with Prometheus. So we will have fun collecting these metrics. We learn more about how Prometheus works. There are people when they start learning about how Prometheus's supporter works. They are confusing because they don't understand very well what are the supporters and how it works. So we want to describe that. And even that, we might save some money because sometimes you create an instance. You suddenly realize that the instant you created before was very huge, and you can't recite it. So we repair it. We wanted, when you want to know if your application is performing well, you probably could see if your node code is OK. Then the last step, maybe you could check if your container has no resources. Last, you can focus on your application. So we prepared a Docker compose with five containers that we were deployed with the project. These containers are the game server that is the CSGO server, the Prometheus server, and the supporters. And in this case, for the supporters, for the node, we use it the node supporter. For the containers, we use it the CSvisor. And for the application, that in this case is the CSGO, is the CRCDS supporter. If we are focusing the CRDS supporter, we show that it's supposed to have a few metrics. So which of those metrics we want to monitor? We will start checking the number of people that is playing the game at the moment. We also could check the map that is being played at the moment also. And also, the metric in this case is always half the value one. You can check in the label the name of the map is being played. And if we are focusing the container metrics, and when you are focusing in the container metrics, you want to assure that your container has no resources. For example, if you see how the memory is doing, you can see when the starts begin, the memory is increasing. And the CPU is more straightforward. The CPU in the beginning, it's either. And when a player joins to the game, the CPU increases. When you see the graph, you can see when the game starts and when it ends. Also, you can see which map is consuming more CPU than the others. Just checking the metric. In the case of the notes metrics, it's more difficult to see. For example, for the memory, it's difficult to see anything because the other containers in the host are consuming more memory than the game server. On the other hand, for the CPU, it's more clear. You can see when the game starts when it ends. And a common mistake that we do when you don't know how many resources your application is using, it's creating an instant with more resources than you need. In order to take care of this, you can check the overview of the resources you are using and recite it accordingly. I told you that you might save some money and you got it. So to let some up, we deployed a game server in a cloud instance. We got the metrics with a Prometheus. We learned which metrics are important. And this project was so fun. I may, the next time, I may deploy it in a Kubernetes cluster so I can be a true cloud native gamer. But that's for the next time. That's all. Thanks, everyone, for listening. Happy evening.