.NET agent log: warning [native] GC Events not available

Hi

This warning is not related to the memory metrics (Heap Sizes, GC, ...). It is related to the fact whether we can capture memory dumps. There is an advanced option in the agent mappings where you can turn on memory dump capturing for .NET. If that is set to OFF - or - if the "automatic" option couldnt turn on that feature in the .NET CLR you will get this log output.

Memory Metrics that you see in the Process Health Dashboard are captured using PerfMon. If you dont get this type of data it is most likely that the windows user account that is used to run your .NET proceses doesnt have privileges to capture this data.

Andi

Thanks Andi, i was looking at the agent log because we were not getting the process metrics for these .net agents.

I was hoping to find the user access warning message in the agent log, however i could find it and this was the only error message in agent log.

I remember seeing those access related error in agent log before. i will check with application team on the user access.

-Sreerag

Andreas,

  We have a similar issue.  Do you know hte specific right to request?  and I want to make sure i understand what id we are talking about.

Are we talking about the id the actually runs the application process...not a dynatrace id per say.

You guessed right it is the user id that runs the application process.

-Sreerag

Actually one usernameon an application is listed as "Network Service"

We troubleshoot this as follows

1) Agent log shows "GC Events not available". Andi's reply explains why it is showing up in agent log.

2) Check to see if there is an access warning on reading perf counters in agent log

3) If yes then it could be access issue. We work with Application Admin to provide application user id access to read perf counters. Key here is perf counter read access.

4) if there is no access warning or you dont see all .Net metrics in DT then it could be that there is no registered perf counters on the app server for those missing metrics. Here we need to get the perf counters in the app server so that the agent can read those.

The command "lodctr /R" could help in rebuild all Performance counters. (I'm not a windows expert so please test this out in test server.)

we found that our app servers didnt had all perf counters. we are working to get those counters added in the app server.

Hope this helps.

-Sreerag

As for the permissions - at least thats true when you run a Windows Performance Monitor Plugin - your user that runs your process shoudl be in the local group called Performance Monitor Users. A more detailed description can be found here: How To Retrieve Performance Metrics with Windows Performance Monitor#UserAuthenticationandPermissions

I assume though that Sreerag's point will most likely be the root cause of your issue