I am at a point in our environment where I want to start defining host groups. I have some key questions however that none of the documentation seems to reach touch on or at least not in the detail I am looking for. Hoping somebody from Dynatrace can answer the following questions please. I was going to just ask support, however I thought it would be good to get these answers on the forum for others as well.
It states in the documentation page that...
"Host groups are sets of hosts. Each group can be configured on the host-group level. This makes it easy to change the settings for a large number of hosts. You can define alerting thresholds and OneAgent update settings on a per-host-group basis."
And below that also states...
"Additionally, host groups affect how process groups are detected. When the same process is running in two different host groups, Dynatrace will create one process group for each host group. This means you can also configure process groups differently depending on which host group they run in. Consequently, services are also grouped per host group. So you can configure services differently per host group."
So what exactly does this mean in more detail?
What if you for example, adjusted the anomaly detection for a specific process , services, etc. before setting up host groups.
Outside of the big inconvenience of not being able to create, modify, or remove host groups within the GUI itself (hope Dynatrace addresses this soon), I would like to hear the pros and cons others have ran into around host groups. I see all the benefits to host groups, but what I am more concerned about are the cons (if any).
Solved! Go to Solution.
Hey Larry R.!
I can't answer all of the questions (especially about upcoming support - though I do know a roadmapped goal exists to allow host group reconfiguration via the UI ["goal" being the operative word]), but I can answer the ones about how things change after adding a host group.
Dynatrace Best Practices would dictate that configuring Host Groups should be one of the first things done (as either part of the OneAgent deployment or soon after deployment). There will be some side-effects if you're trying to configure Host Groups after-the-fact.
I hope this helps!
This is good information! Thank you. We have stayed clear from host groups because it is still not GA and really we were waiting on that. Also, it is not universal and we still have some Solaris hosts.
There are situations that are not solvable without host groups at the moment. Well maybe they are but only with a significant manual effort by reconfiguration of monitored processes.
I definitely agree with the idea to setup host groups before you do any other customization. Setting up host groups after configuration may lead to unexpected results.
Regarding Solaris - I don't think host groups will ever come to this platform. (probably applies to all other PaaS agent versions as well)
You're welcome, Larry R.! Glad to help! 🙂
While it's not GA, Early Adopter Release of Host Groups means that it's a fully supported functionality of our solution (meaning Dynatrace ONE Live Chat and Dynatrace Support will be able to help you with any concerns you have).
For your Kubernetes questions I was able to find this information:
And for Solaris:
All really great info guys. We came into Dynatrace I believe at an odd time when it comes to host groups. I believe that was in the early stages so this was not a consideration at the time of initial deployment.
Thankfully we don't have what I would consider a huge deployment yet so I don't think it will be too painful. Sounds like my best approach now with getting things converted over will be to do it one host group at a time. Do one, give it burn in time so I can see what changes come out of it before moving on to the next one.
Solaris I am just going to ignore as we are actively moving everything left over to Linux so I am not too worried about that anymore. At the time we went with Dynatrace, it was still unclear how fast a migration from Solaris was going to be. Today that picture is much more clear.
I think I am just going to pick one of our smaller groups to start with. Then I can see first hand what sorts of things change and exactly what needs to be addressed. This was my biggest fear that once adding them it would turn things upside down. Kinda makes me wonder how some of the customers with really large Dynatrace deployments made the change to using host groups.