I think there is a inconsistency in the documentation or maybe I'm not seeing something correctly.
Configuration options marked with Dynamic true can be changed at runtime when set from supported sources:
- Central configuration
- Java system properties, but only when set from within the application
In https://www.elastic.co/guide/en/apm/agent/java/current/config-core.html#config-trace-methods trace_methods is marked as dynamic.
But I can't edit trace_methods with remote configuration in Kibana. Do you know why this is?
I've tried the elasticapm.properties configuration (and place it in the same folder as the agent) as well as JVM arguments when starting the application.
I also have a second question: is there any data available about what the overhead would be if my
trace_methods config would by
trace_methods_duration_threshold 100 ms?
The documentation warns for high overhead "The agent will create stack traces for spans which took longer than
span_frames_min_duration . When tracing a large number of methods (for example by using wildcards), this may lead to high overhead. Consider increasing the threshold or disabling stack trace collection altogether" and I was curious if there is also a high overhead if the trace_methods_duration_threshold is set to a high time treshold.
Unfortunately I can't use the async profiler since we use Windows network shares.