Update README.md
This commit is contained in:
parent
21460ea04e
commit
a4f51d34ca
30
README.md
30
README.md
|
@ -1,24 +1,24 @@
|
|||
Dynatrace plugin for Fuel
|
||||
============
|
||||
|
||||
The Dynatrace Fuel plugin introduces two new node roles called *Dynatrace
|
||||
OneAgent* and *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 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.
|
||||
|
||||
Dynatrace OneAgent
|
||||
-------------
|
||||
The *Dynatrace OneAgent* role must be applied to all nodes
|
||||
in your environment that have the Controller role. 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 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.
|
||||
|
||||
Dynatrace Security Gateway
|
||||
-------------
|
||||
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.
|
||||
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.
|
||||
|
|
Loading…
Reference in New Issue