Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Providers 100% Unknown When Using Webserver Logs, Works when Using Javascript Tracking? #17486

Closed
mddvul22 opened this issue Apr 22, 2021 · 5 comments
Labels
answered For when a question was asked and we referred to forum or answered it.

Comments

@mddvul22
Copy link

We are using the free Maxmind GeoLite2-City database with our Matomo install. Our Matomo install is mainly using a nightly import of Apache logs for the majority of the websites being used with our Matomo. For every one of these sites, when you click on Vistors->Locations, and scroll down to Providers, it states that 100% are "Unknown".

However, we have configured one of our websites in Matomo twice: one is using log analytics, and the other is using javascript tracking -- but they are the same URL.

We have found that for the version using javascript tracking, the Provider details work. It is only on the sites using log analytics that Provider is 100% unknown. Do the provider details require javascript tracking? Or is something wrong in our configuration?

Expected Behavior

Since the visitor IP address should be available to Matomo through both methods, I would expect that Provider details wouldn't be dependent upon the javascript tracking.

Current Behavior

It appears that it is dependent upon javascript tracking.

Your Environment

  • Matomo Version: 3.14.1
  • PHP Version: 7.2.24
  • Server Operating System: Centos 8.3
  • Browser: Firefox
  • Operating System: Linux
@mddvul22 mddvul22 added the Potential Bug Something that might be a bug, but needs validation and confirmation it can be reproduced. label Apr 22, 2021
@diosmosis
Copy link
Member

Hi @mddvul22, can you look for an IP that is both in your log file and in your Matomo database and see if the provider is geolocated successfully in the maxmind demo: https://www.maxmind.com/en/geoip-demo? Can you also make sure the IP isn't anonymized in any way in the log files?

@mddvul22
Copy link
Author

mddvul22 commented Apr 23, 2021

Hi @diosmosis Here is an example: at approximately 23:19:41, last night, we had a visit from the IP address 67.225.10.219.
Here is how the javascript tracking shows the visit. You can see the provider is listed:

image

Here is how log analytics shows that visit, with no provider shown:

image

Here is the geoip lookup results for that IP:

image

And, for the purposes of our troubleshooting this issue, we have completely disabled IP anonymization, as you can see here:

image

Finally, here are screenshots of the Providers overviews, from the Locations tabs. First is the website with javascript tracking:
image

And, for comparison, the same website with log analytics tracking:
image

Thanks!

@sgiehl
Copy link
Member

sgiehl commented Apr 23, 2021

Hi @mddvul22 Looking up the provider is disabled by default when importing visits. This was initially implemented to prevent reverse dns lookups to identify the provider. You can disable that default by setting the --enable-reverse-dns for log importer.
Nevertheless I guess we actually could do the geoip lookup in any case, as it shouldn't take long to do it.

@mddvul22
Copy link
Author

Thank you! I've added --enable-reverse-dns to our import command and will run the import with that, tonight. Thanks!

@mddvul22
Copy link
Author

This worked. Thanks!

@tsteur tsteur added answered For when a question was asked and we referred to forum or answered it. and removed Potential Bug Something that might be a bug, but needs validation and confirmation it can be reproduced. labels Apr 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answered For when a question was asked and we referred to forum or answered it.
Projects
None yet
Development

No branches or pull requests

4 participants