Leaving Ackee : data export

[timconsidine]

Much as I like the principle of Ackee, and it works nicely in so far as it goes, it is not as good (IMHO) as Umami.

So I will be uninstalling Ackee but want to get what data I can out.
However I can see no way of doing through the UI.
Something in docs about use GraphQL and the API.
But hardly easy.
Now I have to set up a new system just to get data from my old system.

Any thoughts on how I can get the data out?
Not asking for every last ounce, just main metrics.

[timconsidine]

@timconsidine guess I am going to have to export from the terminal
at least the mongo shell is easily accessible from terminal : well done Cloudron

[timconsidine]

@timconsidine so using the Cloudron app terminal, this seems to work

events :

root@4<appid>:/app/code# mongoexport -u "${CLOUDRON_MONGODB_USERNAME}" -p "${CLOUDRON_MONGODB_PASSWORD}" --host="${CLOUDRON_MONGODB_HOST}" --port="${CLOUDRON_MONGODB_PORT}" --db="${CLOUDRON_MONGODB_DATABASE}" --collection=events --out=/app/data/events.json
2021-09-21T15:07:54.457+0000    connected to: mongodb://mongodb:27017/
2021-09-21T15:07:54.485+0000    exported 0 records

domains:

root@<appid>:/app/code# mongoexport -u "${CLOUDRON_MONGODB_USERNAME}" -p "${CLOUDRON_MONGODB_PASSWORD}" --host="${CLOUDRON_MONGODB_HOST}" --port="${CLOUDRON_MONGODB_PORT}" --db="${CLOUDRON_MONGODB_DATABASE}" --collection=domains --out=/app/data/domains.json
2021-09-21T15:08:22.075+0000    connected to: mongodb://mongodb:27017/
2021-09-21T15:08:22.086+0000    exported 2 records

actions :

root@<appid>:/app/code# mongoexport -u "${CLOUDRON_MONGODB_USERNAME}" -p "${CLOUDRON_MONGODB_PASSWORD}" --host="${CLOUDRON_MONGODB_HOST}" --port="${CLOUDRON_MONGODB_PORT}" --db="${CLOUDRON_MONGODB_DATABASE}" --collection=actions --out=/app/data/actions.json
2021-09-21T15:08:43.450+0000    connected to: mongodb://mongodb:27017/
2021-09-21T15:08:43.479+0000    exported 0 records

records :

root@<appid>:/app/code# mongoexport -u "${CLOUDRON_MONGODB_USERNAME}" -p "${CLOUDRON_MONGODB_PASSWORD}" --host="${CLOUDRON_MONGODB_HOST}" --port="${CLOUDRON_MONGODB_PORT}" --db="${CLOUDRON_MONGODB_DATABASE}" --collection=records --out=/app/data/records.json
2021-09-21T15:09:04.531+0000    connected to: mongodb://mongodb:27017/
2021-09-21T15:09:05.540+0000    [#############...........]  2bd8f6343edd4d20.records  8000/14225  (56.2%)
2021-09-21T15:09:06.089+0000    [########################]  2bd8f6343edd4d20.records  14225/14225  (100.0%)
2021-09-21T15:09:06.089+0000    exported 14225 records

Seems likes records is the primary table.
Hope this helps someone.

[nebulon]

Thanks for sharing, this is always worth it to have a documented flow for such data migration steps

[timconsidine]

@nebulon I learn constantly from everyone here so pleased to share

Would be great to get umami packaged if someone is so kind
I got it installed on CapRover so hopefully it is within viable scope. Would be great to have it in my production Cloudron.

[SansGuidon]

@timconsidine are you still there and using umami?
I want to move away from Matomo which works fine but not so great neither. Ackee seems abandonned so I guess Umami is the viable option, even if 2GB for memory requirements looks a bit overkill but well, the web is bloated.

[timconsidine]

@SansGuidon hi
"using Umami" is an interesting point.
I have umami installed but hardly ever use it (so rarely that I have even forgotten what sites I have configured there).
As far as I recall, it worked fine.
My needs are quite simplistic, and I have lost interest in monitoring traffic to sites.
I should probably take more interest when I have time and motivation !

[luckow]

@SansGuidon umami also works with “higher” traffic, but we had to set the memory limit to 4 GB.

(screenshot shows a time frame of 30 days)