Identify synthetic traffic with DCRUM
Hello Dynatrace, hello Community,
for a test installation we would like to identify synthetic traffic with DCRUM. The synthetic traffic is not coming from a dynatrace tool but from different synthetic agent tool (www.servicetrace.de). This tool does not set a unique Agent String in the HTTP header of its request.
Are there other ways to identify traffic coming from these specific agents so we can flag it as coming form a synthetic agent?
Best regards
Tino
Hi Tino
There are three ways DC-RUM can identify and tag synthetic agents.
- The standard way using something detected in the user agent string as already mentioned in this thread
- By IP address
- By username
So if your traffic always comes from a specific address/address range or if it always uses specific user names and you have username recognition configured you can specify that those are synthetic agents.
Please note though that this is a global CAS setting so if you did configure it using option two or three then all traffic from that IP or username would be considered synthetic.
If this is a suitable option for you you can configure it by doing the following.
First navigate to <casIP>/ApplTypeConf
In this section you can add a syntehtic agent that your traffic can be assigned to. Use the following values
ID: Pick an ID that is not already in the list
User Agent: enter a name for your agent
Protocol: TCP
Real/Syntehtic: Synthetic
Aggreggation schema: -
As below
Now that you have created an agent you then need to assign the traffic to it. To do this navigate to Settings>Report Settings>User-Protocol Mapping
In this screen you can assign you agents using something like the following
ip:23.234.43.101 = -49
Hope this helps.
Regards
Alasdair
Hi Tino,
Cosmin is right, it seems there is no other way than the user string in the HTTP header to track synthetic traffic.
Here is a workaround: If the traffic from servicetrace.de comes from a specific IP address or a set of IP addresses, you can define a site named Servicetrace and create a DMI filtering on the site servicetrace
Hope that helps,
Harshal.
Tino,
The only way I'm aware of tagging the type of traffic is by using the user agent or protocol. Is there nothing in the user agent of the request that is unique to the tool you are using?
-Cosmin
