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

Log analysis: switch from matomo to ELK stack #379

Open
dr0i opened this issue Jul 24, 2018 · 0 comments
Open

Log analysis: switch from matomo to ELK stack #379

dr0i opened this issue Jul 24, 2018 · 0 comments

Comments

@dr0i
Copy link
Member

dr0i commented Jul 24, 2018

Matomo is superslow, 200 lines/sec import.
As the backend is mysqld, this too don't scale nicely. Also eats harddisk away.
The Elastic stack, formerly known as ELK stack, should work smarter, and seems also DSVGO compatible, see https://www.elastic.co/de/webinars/gdpr-compliance-and-elasticsearch.

This is issue has low priority but it should be a reminder, should we make some more bad experiences with matomo, to switch.

Resulting from hbz/lobid-resources#799.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant