Custom log: geo_organization data

[Oceane F.]

Hi all,

I am using a custom log and I am desperatly trying to include the
geo_organization field in it (or the geo_country, geo_region and
geo_city fields either).
These are described as "auto" il the fieldlist.txt document: does that
mean that they have to be generated by the UTM for example?
If they can be "handly" generated, what should be their format?

Thanks in advance,
Best Regards,
Oceane

[Kirk - Actual Metrics]

Hi Oceane,

Yes, they are automatically generated by Urchin at processing time by
doing a reverse DNS lookup on the client's IP.

Kirk
www.urchintools.com
www.urchinexperts.com
www.actualmetrics.com

[Oceane F.]

Hi Kirk,

So if Urchin doesn't succeed into doing the reverse DNS lookup on the
IP, we couldn't directly give it the location of the user?

Thanks,
Oceane


On Dec 4, 7:25 pm, Kirk - Actual Metrics <kirk.mora...@gmail.com>
wrote:

[Kirk - Actual Metrics]

How would you like to give it the location? If that information is
stored elsewhere in the log file, you can create filters to overwrite
these fields. Is this what you're looking to do?

Kirk
www.urchintools.com
www.urchinexperts.com
www.actualmemtrics.com

[Oceane F.]

Hi Kirk,

That's it: actually I have the location written in the log file. For
the moment it is just the town but it is also possible for me to add
the country.
I am using a custom log format.
Actually I don't see what kind of filters I should create: can you
give me more indications about that?

Thanks for your answer,
Oceane

On Dec 8, 2:33 pm, Kirk - Actual Metrics <kirk.mora...@gmail.com>
wrote:

[Kirk - Actual Metrics]

You will need to create Advanced filters, ultimately storing that
information into the appropriate geo location fields. What the filters
look look really depends on where in the log line the data is stored.
Can you post a sample log line, highlighting the town information?

Kirk
www.urchintools.com
www.urchinexperts.com
www.actualmetrics.com

[Oceane F.]

123.123.123.123 09Dec09 10:06:43 "GET /blabla/blibli" 200 1687
"Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)" London

The town information is "London"

Thanks,

Oceane

On Dec 9, 4:56 pm, Kirk - Actual Metrics <kirk.mora...@gmail.com>
wrote:

[Kirk - Actual Metrics]

Hi Oceane,

In that case, you will need to create a custom log format where the
city field populates the appropriate geo location field.

Kirk
www.urchintools.com
www.urchinexperts.com
www.actualmetrics.com

[Oceane F.]

Hi Kirk,

I have already tried to do that: I have defined this field has the
geo_city or the geo_organization field but neither of them worked: the
location is displayed as "unknown".
The only way I could get the location is by putting it in the
cs_username field, but I would actually like to use this field to give
the username...

I thougth that that doesn't work because I didn't use a correct format
to express the location. Am I right?

Thanks,
Oceane


On Dec 10, 8:53 pm, Kirk - Actual Metrics <kirk.mora...@gmail.com>
wrote:
> Hi Oceane,
>

[Jeremy Aube]

Hi Ocean,

I would try something like this:

1. Make a copy of the lib/custom/logformats/fieldlist.txt.sample file
and save it as fieldlist.txt.
2. This creates 25 custom raw fields and 5 calculated fields. You can
remove most of these from the fieldlist.txt file and rename the ones
you want to keep with more descriptive names.
3. Reference these fields in your custom log format.
4. Use advanced filters to override geo_country, geo_region, etc.,
with your custom fields.

Jeremy Aube
http://www.roirevolution.com/urchin

[Oceane F.]

Hi Jeremy,

That is totally working!

Thanks for your help!

Oceane

On Dec 14, 4:06 pm, Jeremy Aube <ja...@roirevolution.com> wrote:
> Hi Ocean,
>
> I would try something like this:
>
> 1. Make a copy of the lib/custom/logformats/fieldlist.txt.sample file
> and save it as fieldlist.txt.
> 2. This creates 25 custom raw fields and 5 calculated fields. You can
> remove most of these from the fieldlist.txt file and rename the ones
> you want to keep with more descriptive names.
> 3. Reference these fields in your custom log format.
> 4. Use advanced filters to override geo_country, geo_region, etc.,
> with your custom fields.
>

> Jeremy Aubehttp://www.roirevolution.com/urchin

[lu...@excentos.com]

Hi Jeremy,

I am also trying to use custom fields, but I did not achieve so far to
fill datamaps with the values from these fields. Can you send me an
example line of the custom log? What I intend is to add more
parametres to the utm request query (field 6: cs_request).
That would be great, because I have no Idea what to try furthermore.

Thank in advance and best regards,

Jan

On 14 Dez. 2009, 17:06, Jeremy Aube <ja...@roirevolution.com> wrote:
> Hi Ocean,
>
> I would try something like this:
>
> 1. Make a copy of the lib/custom/logformats/fieldlist.txt.sample file
> and save it as fieldlist.txt.
> 2. This creates 25 custom raw fields and 5 calculated fields. You can
> remove most of these from the fieldlist.txt file and rename the ones
> you want to keep with more descriptive names.
> 3. Reference these fields in your custom log format.
> 4. Use advanced filters to override geo_country, geo_region, etc.,
> with your custom fields.
>

> Jeremy Aubehttp://www.roirevolution.com/urchin

[lu...@excentos.com]

Hi Jeremy,

I am also trying to use custom fields, but I did not achieve so far to
fill datamaps with the values from these fields. Can you send me an
example line of the custom log? What I intend is to add more
parametres to the utm request query (field 6: cs_request).
That would be great, because I have no Idea what to try furthermore.

Thank in advance and best regards,

Jan

On 14 Dez. 2009, 17:06, Jeremy Aube <ja...@roirevolution.com> wrote:

> Hi Ocean,
>
> I would try something like this:
>
> 1. Make a copy of the lib/custom/logformats/fieldlist.txt.sample file
> and save it as fieldlist.txt.
> 2. This creates 25 custom raw fields and 5 calculated fields. You can
> remove most of these from the fieldlist.txt file and rename the ones
> you want to keep with more descriptive names.
> 3. Reference these fields in your custom log format.
> 4. Use advanced filters to override geo_country, geo_region, etc.,
> with your custom fields.
>

> Jeremy Aubehttp://www.roirevolution.com/urchin

[Jeremy Aube]

If you're adding parameters to the query string, you're not going to
be able to match these with a custom log source. You could, however,
see about matching these to custom fields using filters. You can use
regular expressions to set fields to these values. There are two ways
you could go about doing this:

1. Cannibalize existing fields so that they will report your custom
fields instead.
2. Use custom fields and create datamaps/reports that use those custom
fields.

The first option is often a little easier and may get you exactly what
you need. The second option will require a bit more work, but leaves
your existing reports intact. There are also middle of the road
options that use the custom variables but still cannibalize existing
reports by replacing some of the fields in the datamap with your
custom variables or appending the custom variables to the datamap and
tweaking the report to use the custom variable instead of one of the
existing parameters.

Jeremy Aube
http://www.roirevolution.com/urchin

[lu...@excentos.com]

Thanks, Jeremy, that worked. I now use advanced filters to parse the
cs_request field.

What I don't understand so far is wherefore the Filter examples at the
bottom of the custom_log configuration file are useful. In my opinion,
they are never functional.

Jan-Martin Lurse

On 11 Jan., 13:34, Jeremy Aube <ja...@roirevolution.com> wrote:
> If you're adding parameters to the query string, you're not going to
> be able to match these with a custom log source. You could, however,
> see about matching these to custom fields using filters. You can use
> regular expressions to set fields to these values. There are two ways
> you could go about doing this:
>
> 1. Cannibalize existing fields so that they will report your custom
> fields instead.
> 2. Use custom fields and create datamaps/reports that use those custom
> fields.
>
> The first option is often a little easier and may get you exactly what
> you need. The second option will require a bit more work, but leaves
> your existing reports intact. There are also middle of the road
> options that use the custom variables but still cannibalize existing
> reports by replacing some of the fields in the datamap with your
> custom variables or appending the custom variables to the datamap and
> tweaking the report to use the custom variable instead of one of the
> existing parameters.
>

> Jeremy Aubehttp://www.roirevolution.com/urchin