A company set up an on-premises AppDynamics Controller and an on-premises Events Service cluster. What describes setting up this Events Service cluster?

Question

Options

• AThe Events Service API ports cannot be reconfigured from the default 9080/2081.
• BThe Controller must be able to initiate communication with the Events Service cluster.
• CThe Events Service cluster must be able to initiate communication with the Controller.
• DThere is no need for a load balancer or virtual IP address in front of the Events Service cluster.

• A
  2% (1)
• B
  84% (47)
• C
  5% (3)
• D
  9% (5)

Explanation

The Events Service is the on-premises data storage facility for unstructured data generated by Application Analytics, Database Visibility, and End User Monitoring deployments. The Events Service can be deployed as a single node or a cluster of three or more nodes, depending on the data volume and availability requirements. The Controller and other Events Service clients connect to the Events Service to store and retrieve analytics data. Therefore, it is essential that the Controller is able to initiate communication with the Events Service cluster, using the Events Service API ports (default 9080/2081). The Events Service cluster does not need to initiate communication with the Controller, as it only responds to the requests from the clients. The Events Service API ports can be reconfigured from the default values, if needed, by modifying the conf/events-service-api-store.properties file on each node. However, the clients must also be updated with the new port values. It is also recommended to use a load balancer or a virtual IP address in front of the Events Service cluster, to provide a single endpoint for the clients and to enable load balancing and failover among the nodes.

No community discussion yet for this question.