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
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -222,11 +222,11 @@ When no service call is being traced, the custom request attributes are dropped.
222
222
223
223
<aname="webrequests"/>
224
224
225
-
## Trace web requests
225
+
###Trace web requests
226
226
227
227
<aname="inwebrequests"/>
228
228
229
-
### Trace incoming web requests
229
+
####Trace incoming web requests
230
230
231
231
You can use the SDK to trace incoming web requests. This might be useful if Dynatrace does not support the respective web server framework or language processing the incoming web requests.
232
232
@@ -236,7 +236,7 @@ To trace an incoming web request you first need to create a WebServerInfo object
To trace a specific incoming web request you then need to create a Tracer object. Make sure you provide all http headers from the request to the SDK by calling addRequestHeader(...). This ensures that tagging with our built-in sensor is working.
239
+
To trace a specific incoming web request you then need to create a Tracer object. Make sure you provide all http headers from the request to the SDK by calling addRequestHeader(...). This ensures that tagging with our built-in sensor will work.
int statusCodeReturnedToClient = processWebRequest();
259
259
tracer.setStatusCode(statusCodeReturnedToClient);
260
260
} catch (Exception e) {
261
-
tracer.setStatusCode(500); // we expect, the container sends http 500 in case request processing throws an exception
261
+
tracer.setStatusCode(500); // we expect that the container sends HTTP 500 status code in case request processing throws an exception
262
262
tracer.error(e);
263
263
throw e;
264
264
} finally {
@@ -268,11 +268,11 @@ try {
268
268
269
269
<aname="outwebrequests"/>
270
270
271
-
### Trace outgoing web requests
271
+
####Trace outgoing web requests
272
272
273
-
You can use the SDK to trace outgoing web requests. This might be useful if Dynatrace does not support the respective http library or language.
273
+
You can use the SDK to trace outgoing web requests. This might be useful if Dynatrace does not support the respective http library or language sending the request.
274
274
275
-
To trace a outgoing web request you need to create a Tracer object. It is important to send the Dynatrace Header. This ensures that tagging with our built-in sensor is working.
275
+
To trace an outgoing web request you need to create a Tracer object. It is important to send the Dynatrace Header. This ensures that tagging with our built-in sensor will work.
0 commit comments