AppD Archive

SaaS model and nodes not accessible from external network

CommunityUser
Splunk Employee
Splunk Employee

Hi,

In our set-up, let's say we go with AppD SaaS model where controller is deployed at AppD datacenter, we have application running inside our data center. Not all the nodes where we put AppD agent will be accessible via external ip. In such case how does AppD SaaS model work ? Controller will not be able to communicate to some of the nodes inside our datacenter.

This shall be a common scenarion across your customers I would think so. Appreciate the guidance.

0 Karma

Arun_Dasetty
Super Champion

Hi Sandip,

Sorry for the delay in response. Regarding your queries , Please let us know if the following information helps:

Option-1:

- if your data center is running beside a non-authenticated proxy you can use -Dappdynamics.http.proxyHost -Dappdynamics.http.proxyPort properties, If the agent is running behind a firewal you can just open https port 443 or http port 80 that should be enough for agent controller communication to work

Option-2: if above said is not an option

- you can install an on premise controller in side your data center network and configure agent to point to onpremise contorller  , refer docs for more info http://docs.appdynamics.com/display/PRO14S/Configure+an+On-Premise+Controller

Regards,

Arun

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...