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
When no service call is being traced, the custom request attributes are dropped.
221
222
223
+
<aname="webrequests"/>
224
+
225
+
## Trace web requests
226
+
222
227
<aname="inwebrequests"/>
223
228
224
-
## Trace incoming web requests
229
+
###Trace incoming web requests
225
230
226
-
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.
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.
227
232
228
-
To trace any kind of incoming web request you first need to create a WebServerInfo object. The info object represents the endpoint of your web server (webservername, applicationname and context root). This object should be reused for all traced webrequests for the same application.
233
+
To trace an incoming web request you first need to create a WebServerInfo object. The info object represents the endpoint of your web server (web server name, application name and context root). This object should be reused for all traced web requests within for the same application.
To trace a specific incoming web request you then need to create a Tracer object. It is important to 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 is working.
0 commit comments