Cloud monitoring: cloud monitoring with dynatrace
Ahola, Johannes (2022)
2022
All rights reserved. This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2022120927560
https://urn.fi/URN:NBN:fi:amk-2022120927560
Tiivistelmä
The purpose of this thesis work was to produce visibility and add information’s availability from critical services in multi-cloud environment. OP Financial Group has Amazon Web Services (AWS) and Azure (Microsoft) cloud environments in its use. In this thesis I focused purely on building monitoring on AWS cloud service side. Work with building Dynatrace monitoring on Azure side will continue outside of this work. The topic for this work originated from OP-groups need to build more versatile monitoring on cloud service side, which can be followed from the centralized views and dashboards. The tools which have been used for this purpose is Dynatrace. Same tool has been in use by OP before but in significantly smaller scale on the cloud services side.
This work consists of two parts, theory, and physical implementation. In the theory part, the most common cloud service models, cloud deployment models, and common cloud-monitoring types in different cloud-environments were reviewed. In addition to that, importance of achieving observability in monitoring and the three pillars that belong to it by means of which it is achieved were reviewed. In the thesis work, Dynatrace’s features, and its functionalities were reviewed in detail. In addition to Dynatrace, ten of its competing monitoring services, and their main functionalities are briefly outlined.
As a process from start to finish, the work progressed in the following way: weekly follow-up meetings with the team’s product owner (corresponds to the team leader) and similarly from the school’s side with the guiding teacher, also, meetings with Dynatrace’s representatives were held a few times when planning next steps. For someone who is more dedicated to the subject, going through the terminology and functionality related to cloud services may seem pointless, but this thesis is written from the point of view that, even if the level of knowledge is not on expert level, issues can be understood without major additional re-search.
As example cases for the thesis, views and dashboard for monitoring VPN traffic, traffic of DNS resolver’s, status of Direct Connect and the dashboard which consists all of the mentioned resources were build. After the example cases, the corresponding implementation will be performed for a significantly larger number of resources outside of this work. These examples documented in the work, were prioritized to go first.
This work consists of two parts, theory, and physical implementation. In the theory part, the most common cloud service models, cloud deployment models, and common cloud-monitoring types in different cloud-environments were reviewed. In addition to that, importance of achieving observability in monitoring and the three pillars that belong to it by means of which it is achieved were reviewed. In the thesis work, Dynatrace’s features, and its functionalities were reviewed in detail. In addition to Dynatrace, ten of its competing monitoring services, and their main functionalities are briefly outlined.
As a process from start to finish, the work progressed in the following way: weekly follow-up meetings with the team’s product owner (corresponds to the team leader) and similarly from the school’s side with the guiding teacher, also, meetings with Dynatrace’s representatives were held a few times when planning next steps. For someone who is more dedicated to the subject, going through the terminology and functionality related to cloud services may seem pointless, but this thesis is written from the point of view that, even if the level of knowledge is not on expert level, issues can be understood without major additional re-search.
As example cases for the thesis, views and dashboard for monitoring VPN traffic, traffic of DNS resolver’s, status of Direct Connect and the dashboard which consists all of the mentioned resources were build. After the example cases, the corresponding implementation will be performed for a significantly larger number of resources outside of this work. These examples documented in the work, were prioritized to go first.