matomo-org / matomo-org/docker
log import5 script results in all client-ip's to be 0.0.0.0
- Dominant language
- Shell
- Stars
- 1k
- Forks
- 384
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I am using the docker version of matomo obviously. I am loading data into it using the log script like so:
```
for i in `ls`; do
#echo $i
if [[ $(stat -c "%A" $i) =~ "w" ]]; then
echo $i
/usr/bin/python3 /var/lib/docker/volumes/matmoto_matomo/_data/misc/log-analytics/import_logs.py --url=http://192.168.0.61:8080 --debug --login hanscees@hanscees.con --password "secletvelly" --idsite=1 --recorders=4 $i
echo "just uploaded this file to webstats: "
echo $i
fi
```
This all works file and the dashboard shows all kinds of data.
However, no data where visitors come from in the dashboard.
The default docker matomo image as far as I can see does have geoip2 on board. I have even updated it with my maxmind license.
I have done things like:
```
docker exec -it matmoto-app-1 php ./console usercountry:attribute 2023-05-13,2023-05-14
and
docker exec -it matmoto-app-1 php ./console core:invalidate-report-data --dates=2023-04-01,2023-05-14 --sites=1
```
this gives no errors.
But no geoip data in the dashboard.
The system settings say:
`
Geolocation | geoip2php (continent_code, continent_name, country_code, country_name, region_code, region_name, city_name, postal_code, lat, long)
-- | --
`
Any help would be greatly appreciated.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with misc/log-analytics/import_logs.py and the Docker image configuration, then reproduce the import using the shown command and inspect whether client IP values are preserved. Compare the imported data with the GeoIP2 settings and the usercountry:attribute and core:invalidate-report-data commands. Done means imported visits retain their source IP and the dashboard shows corresponding geolocation data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python, shell
- Domain
- analytics, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100