This page applies to an earlier version of the AppDynamics App IQ Platform.
See the latest version of the documentation.

Skip to end of metadata
Go to start of metadata

On this page:

The topic describes the AppDynamics Events Service, the data store for on-premises Application Analytics, End User Monitoring (EUM), and Database Monitoring deployments. 

About the Events Service

The MySQL database embedded in the Controller stores application metric and configuration data generated by the Controller. While the MySQL database provides effective storage for this type of data, the high-volume, performance-intensive nature of analytics-based data requires dedicated, horizontally scalable storage, which is provided by the Events Service.

If you are installing the server components for End User Monitoring, Application Analytics, or Database Monitoring, you need to use the Events Service.

Database Monitoring uses the instance of the Events Service embedded in the Controller by default. For data redundancy and storage scalability, however, you can configure Events Service storage for Database Monitoring.

If you are using multiple AppDynamics modules that depend on the Events Service, you should configure the modules to use the same Events Service instance or cluster.

If you already have a deployment made up of an on-premises Controller that uses the SaaS EUM Cloud, but now want to take advantage of User Analytics features, you need to install the on-premises EUM Server and configure it to connect to the on-premises Events Service. For more information, see Configure the EUM Server.

Deployment Topology Overview

You can deploy the Events Service to a single node or cluster. A cluster deployment is made up of at least three nodes. Clusters are horizontally scalable, so that you can add nodes to the cluster as your data requirements grow. A cluster also enables you to utilize data replication, which helps to ensure data integrity in the event of a node failure. 

The Controller includes an embedded Events Service instance used by the Database Monitoring product. The embedded Events Service is not meant to be used with production Application Analytics or EUM installations, because it runs on the same machine as the Controller and does not offer data replication or scalability. It may be used for small-scale environments, especially those intended for demonstration or learning purposes. Note, however, that you can not migrate data from the embedded Events Service to a standalone Events Service if you upgrade later. 

Single Node Deployment

In a single-node Events Service deployment, the Controller and other Events Service clients can connect directly to the Events Service node or through a load balancer. Deploying a single node Events Service behind a load balancer allows you to grow the deployment to a multi-node cluster easily, without having to modify the clients.

Multi-Node Cluster

A multi-node cluster is made up of three or more nodes. With a cluster, the Controller and other Events Service clients, the EUM Server and Analytics Agent connect to the Events Service through a load balancer, which distributes load to the Events Service cluster members. In a single node deployment, connect through a load balancer or directly to the Events Service.

The nodes in a cluster swap a large amount of data. For this reason, when deploying a cluster, make sure to install all cluster nodes within the same local network, ideally, attached to the same network switch. 

Hybrid Deployment

In most deployments, the backend platform components of the AppDynamics Application Intelligence Platform—the Controller, Events Service and EUM Server—would all reside either entirely on-premises or entirely in the cloud (as AppDynamics-hosted SaaS components). 

A hybrid deployment, however, uses a mix of the hosting models. It consists of an on-premises Controller and Events Service (for Transaction Analytics and Log Analytics data), along with a SaaS-hosted EUM Cloud and Events Service for storing and serving EUM data. 

While such a hybrid deployment is possible, certain limitations exists. The following features are not available in a hybrid deployment:

Default Ports

The default ports used by the Events Service are:

  • Events Service API Store Port: 9080
  • Events Service API Store Admin Port: 9081

The Events Service cluster members use additional ports for internal communication among the cluster members. All the ports used within the cluster are listed in the Events Service configuration file, conf/events-service-api-store.properties

  • No labels