I'd like to monitor overall and comprehensive OpenStack environment, that is, what I want to do is monitoring all of Computer node, Controller node and VMs.
I don't understand "OpenStack" itself well, so please tell me if you find some mistakes in this article.
Solved! Go to Solution.
These are really good questions. Thank you for asking them.
Answering them one by one:
To sum up, it is recommended to use Security Gateway, as well as deploy OneAgents on both the VMs and OpenStack hosts.
thank you very much for your detailed answer!
OK, I understand the overview of necessary installation as below.
In addition, I'd like to ask more things about licencing and consumption.
1. Is it necessary to purchase both of licences for VMs and OpenStack hosts respectively when we monitor both of them?
dynatrace automatically recognize and start to monitor each hosts that are installed OneAgent into and need some licences per host.
Of course, we can choose to enable/disable monitoring on specific hosts/application/service, but I assume we basically need licence per host, so it is necessary to purchase licences for VMs and OpenStack hosts respectively.
2. If we install OneAgent into not only each VM but also Compute nodes and Controller nodes, how do we consume licences?
I think that dynatrace have two types of licences;
One of them is "Full-stack" monitoring and the other is "Cloud-infrastructure" monitoring.
I assume that we need "Cloud-infrastructure" licence when we monitor Compute nodes and Controller nodes, and on the other hand, we need "Full-Stack" licence for monitoring of VMs managed by OpenStack.
Answering your further questions:
Please let me know if you have other questions or comments.
Thank you for your very kind answers!
Thanks to you, I now have a deeper understanding of OpenStack monitoring!
I'm going to make a trial on OpenStack monitoring in a large environment with dynatrace in the near future.
I care about additional processes for OpenStack on Compute and Controller nodes, too.
Hello @Bartek_Gatz & @kohei-saito
The OpenStack/OpenShift administrators facing issues with the podman commands when the container monitoring enabled for the CRI-O containers.
If we do not enable CRI-O containers then there is no code-level information for the OpenShift/Kubernetes containers.
What could be the reason behind this issue?
Hello @Babar_Qayyum ,
as far as I know podman in general is not supported (in terms of monitoring podman containers). But I think you mention your admins have issues with the podman commands itself. I believe in this case you may want to try disabling monitoring of podman processes by defining your own process monitoring rules.
There are the following built-in container monitoring rules already applied.
Also, the following rules applied process group monitoring.
One more rule in the container monitoring rules.
Still the same issue.
@Babar_Qayyum I don't know your situation, but I think you have your podman rules wrong. AFAIK the podman is a command, not a kubernetes container name and based on your description you have problem with the podman command itself. Thus you should have the rule not to monitor processes where EXE name equals podman.
Maybe you should consider opening a support ticket.
I included the following rule as well now. Will check with the admins and update you.
After implementing all these rules, the admins are still not able to execute the podman commands when the CRI-O container is enalbed.