AppD Archive

How can i see which program/process causes that problem?

CommunityUser
Splunk Employee
Splunk Employee

Hi,

I watch my ISS applications. Their response times are generally too high. And there too many errors like "Memory utilization is too high", "CPU utilization is too high".

My agent show me which method of my ISS application waiting. But I don't need this. Becouse I know that my code is so simple and can run faster while server isn't busy.

How can i see which program/process in the server causes that problem at that time? For example, maybe my an other c# program make an update and this make server busy, or maybe my network out is not good enaugh etc.

Tank you for your responses.

0 Karma
1 Solution

CommunityUser
Splunk Employee
Splunk Employee

Hi Gurkan,

.NET agent instruments the byte code of the application that is configured for. Hence it can only say where the application is taking time from the snapshots. You can look at the call stack in the snapshot to figure out which part of the application is taking time. 

In order to identify which other program/process on the same system is causing this we have two options -
1. If the other program/process is a managed application, you can configure the .NET Agent for the same and monitor the performance of the application.


2. You can monitor any relevant performance counter like Process Counter at the machine level, to see if any of the process is taking more system resources.

However, in both of the above cases, you would need to correlate the data manually, That is, you have to look at the metrics of both the second program/process and perf counter metrics for the same time period manually and figure out why the application in question is taking more time.

On a side note, you can use metric browser to see values of various metrics for your managed application or the performance counter over the time specified in the time range drop-down menu

Hope this helps. Let us know if you need any further information.

Thanks,
Vishnu

View solution in original post

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi Gurkan,

.NET agent instruments the byte code of the application that is configured for. Hence it can only say where the application is taking time from the snapshots. You can look at the call stack in the snapshot to figure out which part of the application is taking time. 

In order to identify which other program/process on the same system is causing this we have two options -
1. If the other program/process is a managed application, you can configure the .NET Agent for the same and monitor the performance of the application.


2. You can monitor any relevant performance counter like Process Counter at the machine level, to see if any of the process is taking more system resources.

However, in both of the above cases, you would need to correlate the data manually, That is, you have to look at the metrics of both the second program/process and perf counter metrics for the same time period manually and figure out why the application in question is taking more time.

On a side note, you can use metric browser to see values of various metrics for your managed application or the performance counter over the time specified in the time range drop-down menu

Hope this helps. Let us know if you need any further information.

Thanks,
Vishnu

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Many thanks for your support.

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 ...