In Framework V1, there is a single scheduled method, the query method.
When that method takes longer than the hardcoded time (60 seconds) to run, a thread dump file is generated in the logs folder of the plugin agent.
On Framework V2 many methods can be scheduled. When one of them runs for longer than the scheduled interval, an ERROR event is sent to the EEC with the method name and how long it took to run.
Maybe we could also send the full thread dump when that happens, to help the extension developer troubleshoot where his code got stuck.
The main challenge is that today the SDK is very lean, it has zero dependencies. We would need to find a way to provide a dump without introducing a dependency.
In Framework V1, there is a single scheduled method, the
query
method.When that method takes longer than the hardcoded time (60 seconds) to run, a thread dump file is generated in the logs folder of the plugin agent.
On Framework V2 many methods can be scheduled. When one of them runs for longer than the scheduled interval, an ERROR event is sent to the EEC with the method name and how long it took to run.
Maybe we could also send the full thread dump when that happens, to help the extension developer troubleshoot where his code got stuck.
The main challenge is that today the SDK is very lean, it has zero dependencies. We would need to find a way to provide a dump without introducing a dependency.
FYI @Dynatrace-James-Kitson