2 of 2 people found this helpful
http_requests.user_agent actually provides the Browser / App being used to access the server, so I'd think it would get you what you need. Did you miss that field, or is there some reason why it won't work for you? Other than that, you're probably going to need to parse logs, which is no fun.
1 of 1 people found this helpful
I skimmed through and missed that. Here is a sample of the results from User Agent. I'm guessing the third and fourth rows are mobile access.
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2;) Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0) Mozilla/5.0 (iPad; CPU OS 9_3_5 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile Mozilla/5.0 (iPhone; CPU iPhone OS 9_3_5 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Mobile/13G36 TableauMobile/18.104.22.168.0 Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/601.4.4 (KHTML, like Gecko) Version/9.0.3 Safari/601.4.4 Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) python-requests/2.7.0 CPython/2.7.9 Windows/2012Server Python-urllib/2.7 Tabcmd/9.3, Build 9300.16.0606.1812; OS Windows Server 2012 R2, version 6.3 Tableau/49.0 CFNetwork/758.5.3 Darwin/15.6.0
Yes. As I recall there are several 3rd party websites that have attempted to document what / who all the agent strings are. There are likely more possibilities than the ones you happen to have you in your server's table at this moment, but you should be able to capture the lion's share using the web sites and "your brain" to read the strings