Service Availability Monitoring

[CommunityUser]

Hello - we are researching using App Dynamics as a service availability monitoring solution (as described here) and had a couple questions that hopefully the community can answer.

We will be using this functionailty to monitor internal and external URLs for status codes and keywords within the response, as the article above describes.  The main question that we have is capacity.  It looks like we need a machine agent , which makes sense, but the question is how many will we need?  Is there a limit to the number of URLs that a single machine agent can have configured? 

I'm sure once we have our licensing set up and ready to poke around in dev, I'll have other questions, but to get the ball rolling I'm just looking for a standard for scaling out this potential environment.

Thanks

Jon

[CommunityUser]

I could be wrong, but I believe the limit is 60 HTTP checks per machine agent.

[CommunityUser]

Thanks.  Is that in the documentation/white papers/knowledge docs somewhere?  Where did you come up with that number?

[CommunityUser · Accepted solution]

After talking with Support, here is a response that was given for future reference:

There is no hard core limit per machine agents but may be we would hit the default max metric limit of an machine agent .  That should not be problem if your controller has the capacity and machine has enough memory. We would recommend 500 URL per machine agent.

We would still recommend to spin up multiple machine agent rather than putting everything on one machine agent. I would recommend you to spin up one and test it performance one at a time. So in case of any issue we can work on it.