Which geolocation provider are you using in Matomo?

We are using,

It's a core plugin from Matomo

And

for Db

@sgiehl any solution for this issue ??

Thanks

It should actually not happen at all. Are you using dbip or maxmind database? and which one? And wher are your visitor many located? Maybe the database returns an invalid value 🤔

We are using dbip database. Visitors are from USA , EMEA and Asia region manily.
Then how we can fix this ??

Paid or free database? Can you see the values of those queries that have too long values?

Actually, we are using GeoLite2-City from MaxMind, Its a free version we are using
Its insert query to piwik_log_visit for column location_region.
There is no data is tracking for this column.

Thanks,

@msonnad if the logging has no value for the region, it actually can't be too long. But maybe it's not printed in the log as some other value contains binary data causing the log to abort.
To avoid that error you can change the sql mode on your server and remove STRICT_TRANS_TABLES I think. That way the values should be truncated instead of throwing an error and not inserting them at all.

We use a Intranet Location Geo plugin.
Our Regions names follow our Intranet Locations. We altered to:
location_region | char(20)
Now all regions fit with our intranet names.

see https://github.com/grzchr15/piwik-geoip2-andintra

@agrzchr15 The location_region column is meant for storing iso region codes. Storing something else is not officially supported and might break again with future updates

Thanks for response
Please suggest a solution where MAXMIND region_names and INTRANET region names could chain in reports

The Idealflow:

Have a GEO plugin which search an IP in a INTRANET IPAM database and populates the log_visit fields
const CONTINENT_CODE_KEY = 'continent_code';
const CONTINENT_NAME_KEY = 'continent_name';
const COUNTRY_CODE_KEY = 'country_code';
const COUNTRY_NAME_KEY = 'country_name';
const REGION_CODE_KEY = 'region_code'; -> either MAXMIND region codes or own region codes
const REGION_NAME_KEY = 'region_name'; -> either MAXMIND region names or own region names
const CITY_NAME_KEY = 'city_name';
const AREA_CODE_KEY = 'area_code'; -> either MAXMIND region names or own area codes
const LATITUDE_KEY = 'lat';
const LONGITUDE_KEY = 'long';
const POSTAL_CODE_KEY = 'postal_code';
const ISP_KEY = 'isp';
const ORG_KEY = 'org';

If the IP is not found in INTRANET IPAM chain to the "offical" MATOMO GEOIP plugin, and populate again this values.

Currently we can select one single GEOIP plugin ( webserver, php, ) but no Chaining hook is available.
"offical" MATOMO GEOIP plugin does not support any connection to INTRANET IPAMs.

All reports which use geo information can so work only with maxmind. Storing it not in the same values would need to duplicate all reports if collected elsewhere.

Having just a bit more field size seems still the least impact to make matomo more useful and not to break lots of other things.

If there is any chaining possible in matomo geo plugin, this would allow to select a GEO intranet plugin and the chain to the normal MATOMO GEO plugin ( and no patching every release) .

So to topics:
1.) Chaining
2.) SQL field sizes versus complete new sets of reports, and tables
3.) Missing opportunity to get a report how many users from internet/intranet for a website.

Isn't it duplicate of #19323?
Then can be closed, as #19323 has been solved

No, at #19323 it just reacts on some regions from maxmind which are sometimes to long.

This request tries to find a way to have 2 locations providers chained.
Websites are accessed by internet and intranet locations
And intranet location dbs from ipam use same fields at maxmind but longer names like codes for office locations.
So alter table can extend field sizes but this does not solve chaining of loc providers (see above)

currently chaining means patching geo location provider and add ipam based location provider before. In case of not found in intra ipam it continues to maxmind based.

if chaining option would be existing it would be a stable second geo plugin.