You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+5-7Lines changed: 5 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,9 @@
1
+
**Disclaimer: This SDK is currently in early access and still work in progress.**
2
+
1
3
# Dynatrace OneAgent SDK for Java
2
4
3
-
This SDK allows Dynatrace customers to instrument java applications. This is useful for technologies where no out of the box sensor
4
-
is provided or in customer application are monitored.
5
+
This SDK allows Dynatrace customers to instrument java applications. This is useful to enhance the visibility for prioritary frameworks or custom framework not directly supported by Dynatrace OneAgent out of the box.
6
+
5
7
It provides the java implementation of the [Dynatrace OneAgent SDK](https://github.com/Dynatrace/OneAgent-SDK).
6
8
7
9
## Package contents
@@ -32,14 +34,10 @@ If you prefer to integrate the SDK using plain jar file, just download them from
32
34
The Dynatrace OneAgent SDK for Java has no further dependencies.
33
35
34
36
### Troubleshooting
35
-
As long as the SDK can't connect to agent (see usage of SDKState in samples), you might set the following system property to print debug information to standard out:
37
+
If the SDK can't connect to the OneAgent (see usage of SDKState in samples) or you you don't see the desired result in the Dynatrace UI, you might set the following system property to print debug information to standard out:
36
38
37
39
-Dcom.dynatrace.oneagent.sdk.debug=true
38
40
39
-
As soon as SDK is active, but no paths are shown in Dynatrace UI, enable the agent debug flag:
40
-
41
-
debugOneAgentSdkJava=true
42
-
43
41
This will provide SDK related debug information in agent log. Additionally ensure, that you have set an `LoggingCallback` in your application. For usage see class `StdErrLoggingCallback` in `remotecall-server` module (in samples/remotecall folder).
0 commit comments