Is AppEnsure an agent-based solution?

| By:

Yes. The AppEnsure solution requires agents to collect the detailed pertinent information to understand every hop across the infrastructure. The number of agents deployed dictates the broadness of visibility across the infrastructure. Most of our customers start by deploying agents on business-critical application servers or users that seem to have the most problems. For security reasons, the agents only push information to the master appliance; the master appliance never talks to the agents.

Is owning Splunk in addition to AppEnsure necessary?

| By:

No. AppEnsure has developed an the AppEnsure App for Splunk Enterprise to work and enhance the data collected for existing Splunk users, but it is not necessary to have a Splunk license for AppEnsure to show its value.

How current is the application topology displayed in the AppEnsure solution?

| By:

AppEnsure uses an auto discovery design, discovering application flows and mapping topology and user response times from these flows to create the application topology and update that topology in near real time as changes occur—all without user configuration steps. This allows for excellent “out-of-the-box” support for a large number of applications including custom apps. These capabilities significantly reduce the resources required to configure service models and operate the product.

What ports does AppEnsure use?

| By:

AppEnsure agents use port 7443 to communicate outbound only with the master. The master uses port 443 to communicate with the support portal. Internally the master users the following ports:

  • 3000: Inter module polling communication
  • 3001: Generating and validating handshake key
  • 8161: ActiveMQ web console
  • 61616: ActiveMQ default port
  • 7654: AppEnsure DB

Can I use IP addresses or DNS CNAMES?

| By:

AppEnsure fully supports DNS and recommends the use of CNAMES or aliases. Wherever a server name is used you may either use the IP address, server name or alias, if you have set one up in the DNS.