|Dirk Wallerstorfer a4f51d34ca Update README.md||2 years ago|
|deployment_scripts/puppet||2 years ago|
|doc||2 years ago|
|repositories||3 years ago|
|specs||2 years ago|
|.gitignore||2 years ago|
|LICENSE||3 years ago|
|README.md||2 years ago|
|components.yaml||2 years ago|
|deployment_tasks.yaml||2 years ago|
|environment_config.yaml||2 years ago|
|metadata.yaml||2 years ago|
|node_roles.yaml||2 years ago|
|pre_build_hook||3 years ago|
|tasks.yaml||2 years ago|
|uninstall.sh||2 years ago|
The Dynatrace Fuel plugin install the Dynatrace OneAgent on all controller nodes and introduces a new node role called Dynatrace Security Gateway. In order to work properly you need an active Dynatrace account (free trial also works) and access to your SaaS account or a Dynatrace Managed node/cluster on premise.
The Dynatrace OneAgent is automatically installed on all controller nodes, as soon as the plugin is activated. The OneAgent instruments the OpenStack services and also the supporting services like MySQL, RabbitMQ, Memcached, HAproxy, … and sends all monitoring and log data to the node with Dynatrace Security Gateway role.
The Dynatrace Security Gateway role must be applied to a standalone physical machine, where no other OpenStack service is running. If you plan to use Dynatrace for monitoring your applications that run on top of OpenStack as well, you need to make sure that the VMs where the Dynatrace OneAgent is installed have network access to the Dynatrace Security Gateway node.