topic Re: how to use the TA-uas_parser in All Apps and Add-ons

how to use the TA-uas_parser

cdm33 — Thu, 17 Jan 2013 19:46:38 GMT

i've installed it but how do you use it ?

Re: how to use the TA-uas_parser

Ayn — Thu, 17 Jan 2013 19:59:28 GMT

There's info available on the app page: http://splunk-base.splunk.com/apps/48017/ta-uas_parser (also look at the review which has an example on how to use the lookup...)

Re: how to use the TA-uas_parser

cdm33 — Thu, 17 Jan 2013 20:13:02 GMT

there is info on the page - but no instructions on how to actually use it !!

Re: how to use the TA-uas_parser

cdm33 — Thu, 17 Jan 2013 20:14:17 GMT

there's info on the page but no instructions on how to use it !!!

Re: how to use the TA-uas_parser

Ayn — Mon, 28 Sep 2020 13:08:13 GMT

It's a lookup, so you call it like you would with other lookups. As the example in the review shows, it expects the input field to be called "http_user_agent".

Re: how to use the TA-uas_parser

dshpritz — Fri, 18 Jan 2013 21:24:47 GMT

Basically, once it is downloaded, you need to run the script to update the data file. After that you can use the lookup. It does expect that the field you are looking up is "http_user_agent", but if your field extractions are different than that, you can use the rename command:

Let's say your field that you want to lookup is named "user-agent":

index="weblogs" | rename user-agent AS http_user_agent | lookup uas_lookup http_user_agent

Your events should now have the additional fields.

Thanks,

Dave

Re: how to use the TA-uas_parser

splunkears — Mon, 28 Sep 2020 15:19:22 GMT

Though this tip was useful, I found the app TA-uas_parser DEAD slow. while using with
a query like the following:

index="weblogs" |
rename user-agent AS http_user_agent |
lookup uas_lookup http_user_agent | stats dc(myUserApp) by os_family

any tip on making this run faster?

Re: how to use the TA-uas_parser

dshpritz — Wed, 20 Nov 2013 18:46:18 GMT

Hey splunkears,

Yeah, I'm afraid it can be sluggish, especially if the search returns a lot of values. You could also try out the TA-browscap plugin to see if that is any faster. Another possibility is to create a summary search that runs the lookup in the background to populate the summary index. This way you would have the user-agent string parsing done ahead of time.

Thanks,

Dave