The Enterprise Console is the installer for the Controller and Events Service. You can use it to install and manage the entire lifecycle of new or existing on-premises AppDynamics Platforms and components. The application provides a GUI and command-line interface.
There is no customer-facing application for SaaS Controllers since they are managed by the AppDynamics Operations team.
If your Enterprise Console host goes down, it does not impact Controllers, Events Service, or High Availability (HA) pairs. Those services will continue to run independently of the application. You can then discover all platforms on a new Enterprise Console host without any impact on the components.
Enterprise Console Details
The Enterprise Console encompasses management features, installation modes, and lifecycle monitoring.
Enterprise Console Features
The Enterprise Console allows you to perform the following tasks:
HA-Lifecycle Management (Available on Linux only)
Platform Install Modes
There are two install types that you can use to deploy your platform:
On the Platforms page, you can see all of your platforms, their statuses, and the statuses of their services. Once you have selected a platform to view, the screen is separated into different tabs:
Hosts are the actual hardware devices that are connected to the platform. You can add, remove, or change the credentials of your hosts in this tab.
The Controllers page shows the primary and secondary roles of the Controllers and their MySQL nodes. The entire lifecycle operations of Controllers and MySQL nodes can be performed here. You can also see the External URL, which is the IP of the primary machine. Health statuses for the Controllers are also available. You can Add a Secondary Controller if you would like to create an HA pair, then initiate an HA failover if you want to trigger a failover. You can also start or stop a Controller, Upgrade a Controller and MySQL, and more.
The Events Service page displays your Events Service cluster, which can be made using one to three machines. Again there is an entire lifecycle of operations you can do.
Credentials are your host's usernames and private keys. They are required to SSH or connect to the hosts via system user name and private keys.
All of the jobs that you perform on your platform can be seen on the Jobs page. It is a nice way to keep track of your jobs and also see which jobs have failed.
Configurations are important since they let you customize your installations. Configuration settings on the Enterprise Console are separated into three categories: Platform, Controller, and Events Service Settings.
The Controller Settings contains the most configurable settings. The AppServer Configurations under Controller Settings allows you to see all of the Domain configurations which you can initiate from this point or configure your ports. The Database Configurations lets you edit your MySQL settings. So you do not have to tweak the machine, you can do everything from the Console itself.
The following diagram depicts five platform examples that can be deployed and managed by the Enterprise Console.
Depending on the scale of your deployment, your requirements, and the products you are using, your own application environment is likely to consist of a subset of the components shown in the diagram.
You can find the full On-Premises Deployment Architecture diagram on AppDynamics Application Performance Monitoring Platform, as well as a more detailed On-Premises and SaaS architecture diagram on PDFs.
Enterprise Console Platforms
The following table describes how the components work together in the above platforms.
Enterprise Console Platform Connections
The following table lists and describes the traffic flow between the above components in the platforms.