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

New Config for Log-Import: Filter by Site-ID while --replay-tracking #10122

Closed
peterbo opened this issue May 4, 2016 · 2 comments
Closed

New Config for Log-Import: Filter by Site-ID while --replay-tracking #10122

peterbo opened this issue May 4, 2016 · 2 comments
Labels
answered For when a question was asked and we referred to forum or answered it.

Comments

@peterbo
Copy link
Contributor

peterbo commented May 4, 2016

An option to filter by a Site-ID while importing (with replay-tracking) would be a handy feature. In most cases, Webserverlogfiles contain many Site-IDs. At the moment, it's not possible to import just one or multiple specific IDs, but instead, every Site-ID is imported which was found in the logfile.

To select just one or multiple specific Site-IDs which should be imported could be great in the following cases:

  • Migrating a single/multiple specific Site-ID into another instance (at least the lookback window to not have a peak in "New Visitors" metric)
  • When you have a mixed setup, some Site-IDs use Javascript tracking, others App-Tracking, others logimport with replay-tracking, you only want the ladder to be imported by the logimporter
  • You can store standardized testdata in just one file and just import the datasets you need at the moment
  • When the serverside tracking fails (for reasons...) and you use the logimporter (replay-tracking) to catch up to the most recent data state, you want to import the most important Site-IDs first and then the rest (or just specific Site-IDs at all).
@quba
Copy link
Contributor

quba commented May 5, 2016

I think that's a better place to add such a feature request: https://github.com/piwik/piwik-log-analytics
I agree that it can be useful but it is also possible to achieve the same with a small bash script (just a few lines).

@peterbo
Copy link
Contributor Author

peterbo commented May 5, 2016

Oh heck, you're right. Missed that the Logimporter got its own Repo by now. Closing the issue here and reopening there.
To solve the issue with a workaround is not a problem at all. But why working around an issue which could be integrated into core and then be used by everybody?

Reopened in the correct repo here: matomo-org/matomo-log-analytics#137

@peterbo peterbo closed this as completed May 5, 2016
@tsteur tsteur added the answered For when a question was asked and we referred to forum or answered it. label May 5, 2016
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

3 participants