topic Re: Dynatrace OneAgent is not able to activate deep monitoring for this Go process because no symbol table is detected in Container platforms

Dynatrace OneAgent is not able to activate deep monitoring for this Go process because no symbol table is detected

jobin_jose — Sun, 09 May 2021 05:40:14 GMT

We are getting error on Kube-Proxy in Azure kubernetes that 80% of the connectivity dropped to this process. The error showing in DT is "Dynatrace OneAgent is not able to activate deep monitoring for this Go process because no symbol table is detected ". aks-kube is a process running in GO and is managed by Microsoft. Is tehre anyone who faces the same problem? Please help.

Re: Dynatrace OneAgent is not able to activate deep monitoring for this Go process because no symbol table is detected

skrystosik — Thu, 01 Aug 2019 10:29:16 GMT

Here you have information in docs about this limitation:

https://www.dynatrace.com/support/help/shortlink/go#application-must-contain-a-symbol-table

There is avilable workaround as well but I'm not sure if it possible to execute in your example:

OneAgent relies on information stored in the application binary files symbol table. By default, Go generates a symbol table into the application binary, but this can be suppressed by command line parameters or external tools like strip.

go run

The rarely used go run <application> command builds and runs the application on the fly. Because the output application file is temporary (deleted automatically after application termination), the application binary is generated without a symbol table. OneAgent therefore cannot monitor the generated application.

Sebastian

Re: Dynatrace OneAgent is not able to activate deep monitoring for this Go process because no symbol table is detected

echwallah — Mon, 20 Sep 2021 10:45:29 GMT

This is insightful as it typically describes a current client issue. I seem to not get what the solution is.

Could you state clearly how to resolve this?