Discussion Feed

Madan.Kumar · ‎06-24-2019

unsure where you picked up the 200 from. - 200 is the dafault max number of BT's per application which can be changed on on prem-controllers or standalone SaaS controllers. (This has no relation with the issue in your hand) - Looks like you hit the max number of app agent metrics an agent can register with the controller. By dafault this number is throttled at 5000. The number 500 is choosen with the performance in mind, you can increase this number at your agent config level, their should be some documentation around this on appdynamics docs page. But the actual question you need to answer why do you need to track so many metrics from one machine, as going above that number means more overhead on the application server which is not nice for a production machine.

Madan.Kumar · ‎06-24-2019

@Abhilash.C Interesting set of log entries, I have seen similar behaviour when you have more than one node agent with the same name reporting under the same application, especially with the combination of server visibility + .NET agent and machine agent messing around. I have too little context on the infra you are runiing on or the history of the issue, and no access to full log details[Please don't post the logs here I am aginst people doing it] I would say delete your logs and rung the agent for a couple of minutes and then copy the log file and read through every line, this will probably give better context of whats happenning. Appdynamics support used to be great in dealing with issues of this sort, good luch getting your problem sorted by the @support team

Madan.Kumar · ‎04-06-2018

Good to know you got it working. Really nice to see you are using webhook instead of msnd.

Madan.Kumar · ‎04-05-2018

Hi, This happens when the remote SSL cert [CA certificate of your ITSM tool] is not in the trust store of the controller. If it's an on-premise controller you can import the cert into the Java trust store to solve the issue. If you are on SAAS controller, get in touch with the support they can import the cert on your controller. I have seen Appd support to be pretty good at this.

Madan.Kumar · ‎04-05-2018

Doable. Have done an event integration to TSOM in one of my previous workplaces. You will not be able to send in performance metrics though. Two ways to do this, one would be with Webhooks, second would be the more familiar way for all BMC users, the msend I mostly did it old school msend way, below 4 pointers might help you plan but it's still a lot of heavy lifting you will have to do on BEM to get this right. 1. Create a remote cell in Truesight [Idea here is to forward events from appdynamics to this cell and forward to mastercell for processing] 2. Under appdynamics actions create a custom action to execute a script, which will call the msend with the event details as arguments. [Strongly recommend you first decide on the mappings between appdynamics slots and truesight slots] 3. You will have to create MRL file with rules on the remote cell server for refine, de-dupe and auto closure 4. Recompile, reload and test out.

Madan.Kumar · ‎04-05-2018

Your log shows a lot of exceptions relating to Network communication, check the exceptions under your application on the controller, you will see most of these listed in their as well. Check the network connectivity between the application server and the controller on the designated port. I strongly advise you to approach support if the issue persists. st.GetRequestStream() at AppDynamics.Shared.Communication.sg.qs(Byte[] , String ) at com.appdynamics.ee.rest.controller.request.sd.wap()] 2018-04-01 19:59:01.7800 6448 w3wp 3 11 Warn AgentErrorProcessor Agent error occurred, [name,transformId]=[com.appdynamics.CONFIG.ConfigurationChannel - System.Net.WebException,11] 2018-04-01 19:59:01.7800 6448 w3wp 3 11 Warn AgentErrorProcessor 4 instance(s) remaining before error log is silenced 2018-04-01 19:59:01.7800 6448 w3wp 3 11 Warn AgentErrorProcessor 499 instance(s) remaining before instrumentation point is targeted for neutralization 2018-04-01 19:59:01.7800 6448 w3wp 3 11 Error ConfigurationChannel Exception: The operation has timed out Exception: System.Net.WebException: The operation has timed out at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context) at System.Net.HttpWebRequest.GetRequestStream() at AppDynamics.Shared.Communication.sg.qs(Byte[] , String ) at com.appdynamics.ee.rest.controller.request.sd.wap()

Madan.Kumar · ‎04-05-2018

Whenever you instrument an IIS application you will have to go through the below checklist. Please check if you did these in the exact same sequence. 1. Install Agent 2. Configure Agent 3. Restart Agent co-ordinator service 4. Reset IIS 5. Simulate traffic and make sure the tier, node, and the simulated load are captured in appdynamimcs.

Madan.Kumar · ‎04-05-2018

Mate, DO NOT post your agentlogs on community site. Delete these if possible.

Madan.Kumar · ‎04-04-2018

agentlog is your only friend when you are looking to answer a question of "Why"

Date Registered	‎04-21-2017 11:20 PM
Date Last Visited	‎07-02-2019 07:04 PM
Total Messages Posted	10
Total Kudos Received	3

Discussion Feed

Re: Metric Registration Limit Reached and nodes St...

Re: App Agent Not Reporting

Re: BMC TrueSight integration

Re: HTTP request for integrating APPD with ITSM to...

Re: BMC TrueSight integration

Re: App Agent Not Reporting

Re: App Agent Not Reporting

Re: App Agent Not Reporting

Re: App Agent Not Reporting