Skip to content

Commit d7f5d83

Browse files
committed
fix README.md
1 parent 24cc7c1 commit d7f5d83

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

README.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Additionally you should/have to ensure, that you have set a `LoggingCallback`. F
4545

4646
# API Concepts
4747

48-
Common concepts of the Dynatrace OneAgent SDK concepts are explained the [Dynatrace OneAgent SDK repository](https://github.com/Dynatrace/OneAgent-SDK).
48+
Common concepts of the Dynatrace OneAgent SDK are explained the [Dynatrace OneAgent SDK repository](https://github.com/Dynatrace/OneAgent-SDK).
4949

5050
## Get an Api object
5151

@@ -92,14 +92,14 @@ To trace any kind of remote call you first need to create a Tracer. The Tracer o
9292
OutgoingRemoteCallTracer outgoingRemoteCall = OneAgentSDK.traceOutgoingRemoteCall("remoteMethodToCall", "RemoteServiceName", "rmi://Endpoint/service", ChannelType.TCP_IP, "remoteHost:1234");
9393
outgoingRemoteCall.setProtocolName("RMI/custom");
9494
outgoingRemoteCall.start();
95-
try {
96-
String tag = outgoingRemoteCall.getDynatraceStringTag();
97-
// make the call and transport the tag across to server
98-
} catch (Throwable e) {
99-
outgoingRemoteCall.error(e);
100-
} finally {
101-
outgoingRemoteCall.end();
102-
}
95+
try {
96+
String tag = outgoingRemoteCall.getDynatraceStringTag();
97+
// make the call and transport the tag across to server
98+
} catch (Throwable e) {
99+
outgoingRemoteCall.error(e);
100+
} finally {
101+
outgoingRemoteCall.end();
102+
}
103103
```
104104

105105
On the server side you need to wrap the handling and processing of your remote call as well. This will not only trace the server side call and everything that happens, it will also connect it to the calling side.

0 commit comments

Comments
 (0)