Discussion Feed

The reasons for exploring the AppDynamics customization route are: 1. AppDynamics already inspects requests 2. Rolling out to the scale of so many application is easy as they all already have AppdYnamics configured. 3. Due to the impact on each of those 80 odd applications, we wanted to keep them outside of the application code. 4. If we could do it at appdynamics, we can avoid impact on so many applications and that save us regression effort and centralization of code related to this audit rather than distribution of same with each application. ... View more

Thank you Peter for your suggestions so far.   Some of the challenges with the afore mentioned solution would be: 1. The rule I had mentioned was one simple rule and there are many others that need to be applied. 2. The approach intends to capture the field into appdynamics schema. With the scale of inputs & applications, this would quickly grow to unmanageable size and with AppDynamics on MySQL, this would start to deteriorate the performance. There are usually multiple fields per form per application that we need to run the rules through. This would work if we could report to the appdynamics controller only if there is negative hit on the rules which is usually rare (maybe less than 5% of the time).   I was hoping that there could be some means of hooking into appdynamics given that request level stats are already being pulled out (like url, User Principal etc). The last route on my mind is to extend the machine agent and start listening into the HTTP ports on all the requests coming in, then apply the rules and report back to controller (very reluctant on this approach as it complicates on SSL, HTTP port listening etc) ... View more

For now we are looking to only send alerts to the audit team though in the future would not rule out more functionality addition as a reaction. A simple rule is that any mention of "religion" or "race" as part of the many input entries of these 80 odd applications need to be alerted as these are cases of possible favouritism that needs additional audit scrutiny. So the rule screens for matches of mention of religion or race on all the inputs coming in the Http request. ... View more

Ok...here we go. We have 80 odd applications supporting a legal regulation. As part of the regulation, we need to run some generic rules against the input submitted by end users. We have appdynamics already monitoring all these applications and are hence looking to extend appdynamics agent (machine or application) to extract the parameters from request and run the rules and report to controller if there are any issues found. We can then schedule alert emails based on the events reported. ... View more

Setting  <node-name>mylocalserver</node-name> in <java-agent-dir>\ver4.3.5.0\conf\controller-info.xml   resolved my issue and controller started showing load. ... View more

We would want those to be reported back to the controller and then we could allow configuration of alerts based on the reported custom attributes. ... View more

Sorry that I was lost in my exploration that did not revisit this thread.   In more detail, we wish to write some generic validations for our entire suite of applications (not specific to one application) on the input from end users. Data Collectors is what we are looking for - but we cannot configure as there are many applications. So we wish to extend the agent (App Agent or Machine Agent) to inspect the HTTP Request for this purpose.   Looking for guidance on the approach to follow to achieve this: 1. Should we be looking to customize the app agent or machine agent for this? 2. Can we use the SDK API?? https://github.com/qldong/java-sdk/tree/master/application-agent-api ... View more