Recently i was checking on a response degradation anomaly reported by dynatrace AI problem, the slowness was due to the queue wait happened on the weblogic connection pool but the root cause analysis could not able to link this slowness to the resource starvation so we find the slowness root cause reported misleading unless if we were able to track the resource usage to the response time degradation
Just very basic JVM metrics will be available for WebLogic. For other metrics you will have to use JMX queries as @Gautier B. suggests.
But I would highly recommend not to use the JSON method, but apply for the early access of JMX editor. See this blogpost: https://www.dynatrace.com/blog/jmx-plugins-editor-now-available-eap/