NET (Agent, Installation)

cancel
Showing results for 
Search instead for 
Did you mean: 

Web Service requests & Data collector

Web Service requests & Data collector

All,

I have a couple of qns

 

1. Does enabling data collector (http/non-http) increase storage or it doesn't as the data get collected only as frequent as the snapshot collection?

 

2. We have a some mainframe CICS web service requests made from a .NET tier. Does CICS web requests supposed to get auto-discovered out of the box? Or do we need to create a custom exit point?

 

A quick response would be very hepful.

 

Thanks!

Web Service requests & Data collector
6 REPLIES
Employee

Re: Web Service requests & Data collector

Hi Sundarapandian,

 

Please find the answers below-

 

1. Does enabling data collector (http/non-http) increase storage or it doesn't as the data get collected only as frequent as the snapshot collection?

    Answer -> If i understand correctly, you are referring here the performance overhead after creating the Http data collector and MIDC ? If yes, Http data collector is invoked whenever there is snapshot captured. Adding http data collector, add some negligible overhead. However if the frequency of snapshot is high than normal rate then application might have some overhead.So,it is calculated based on frequency of snapshot. And when you create MIDC, The overhead depends on the ByteCode instrumentation. If the instrumentation is happening on short running methods then it will add negligible overhead for each execution.So, based on your MIDC definitions the overhead will be calculated.

 

2. We have a some mainframe CICS web service requests made from a .NET tier. Does CICS web requests supposed to get auto-discovered out of the box? Or do we need to create a custom exit point?

   Answer -> If you are making call to mainframe services over HTTP or SOAP protocol then .Net agent is able to detect the exit call OOTB and if you are making call to mainframe services over Socket then we need to do the some custom configuration to detect the exit call.

 

Please let us know, if you have any question.

 

Thanks,

Ashish.

Employee

Re: Web Service requests & Data collector

Hi Sundarapandian,

 

Please find the answers below-

 

1. Does enabling data collector (http/non-http) increase storage or it doesn't as the data get collected only as frequent as the snapshot collection?

    Answer -> If i understand correctly, you are referring here the performance overhead after creating the Http data collector and MIDC ? If yes, Http data collector is invoked whenever there is snapshot captured. Adding http data collector, add some negligible overhead. However if the frequency of snapshot is high than normal rate then application might have some overhead.So,it is calculated based on frequency of snapshot. And when you create MIDC, The overhead depends on the ByteCode instrumentation. If the instrumentation is happening on short running methods then it will add negligible overhead for each execution.So, based on your MIDC definitions the overhead will be calculated.

 

2. We have a some mainframe CICS web service requests made from a .NET tier. Does CICS web requests supposed to get auto-discovered out of the box? Or do we need to create a custom exit point?

   Answer -> If you are making call to mainframe services over HTTP or SOAP protocol then .Net agent is able to detect the exit call OOTB and if you are making call to mainframe services over Socket then we need to do the some custom configuration to detect the exit call.

 

Please let us know, if you have any question.

 

Thanks,

Ashish.

Employee

Re: Web Service requests & Data collector

Hi Sundarapandian,

Please find the answers below-

1. Does enabling data collector (http/non-http) increase storage or it doesn't as the data get collected only as frequent as the snapshot collection?
Answer -> If i understand correctly, you are referring here the performance overhead after creating the Http data collector and MIDC ? If yes, Http data collector is invoked whenever there is snapshot captured. Adding http data collector, add some negligible overhead. However if the frequency of snapshot is high than normal rate then application might have some overhead.So,it is calculated based on frequency of snapshot. And when you create MIDC, The overhead depends on the ByteCode instrumentation. If the instrumentation is happening on short running methods then it will add negligible overhead for each execution.So, based on your MIDC definitions the overhead will be calculated.

2. We have a some mainframe CICS web service requests made from a .NET tier. Does CICS web requests supposed to get auto-discovered out of the box? Or do we need to create a custom exit point?
Answer -> If you are making call to mainframe services over HTTP or SOAP protocol then .Net agent is able to detect the exit call OOTB and if you are making call to mainframe services over Socket then we need to do the some custom configuration to detect the exit call.

Please let us know, if you have any question.

Thanks,
Ashish.

Re: Web Service requests & Data collector

Hi Ashish,

 

Thanks much for the response.

 

AppDev confirmed these are SOAP XML calls but they they seem to be not discoverd OOTB. I'm trying trying to create custom exit points. I'll update how it goes...

 

Thanks!

Moderator

Re: Web Service requests & Data collector

Hi Sundarapandian,

 

  Thanks for the update. Let us know how it goes. 

Just to make sure we are not simming anything, are these calls made asynchronoulsy ? If yes we might have to enable if already not done so 

https://docs.appdynamics.com/display/PRO43/Thread+Correlation+for+.NET

 

Thanks,

Raunak

Re: Web Service requests & Data collector

Hi Raunak,

 

Yes, the thread correlation has been enabled.

 

We created custom exit points with fully qualified method/class which did not pick the calls.

 

We now have enabled find-entry-points and trying  to also do agent restart and iisreset to see if that helps

 

Thanks,

Sundar