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

Simplify Visitor Generator > Use piwik access logs #2458

Closed
mattab opened this issue May 30, 2011 · 1 comment
Closed

Simplify Visitor Generator > Use piwik access logs #2458

mattab opened this issue May 30, 2011 · 1 comment
Assignees
Labels
Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Milestone

Comments

@mattab
Copy link
Member

mattab commented May 30, 2011

Code for the visitor generator is old and does not use the tracking API, instead it rebuilds tracking requests manually.

Instead, Visitor Generator should take a "Piwik access logs" (requests to piwik.php) from demo.piwik.org by default (but possible to put your own custom access logs) and it should replay this log file, for N days and playing it M times per day.

the other advantage is that this will be usable for API consumers who wish to "initiate" piwik DB with a fixed set of data and run their own tests on it (rather than the current "random" data sets).

Also, logs will be more "standard" and not use the many random strings etc.

@mattab
Copy link
Member Author

mattab commented May 31, 2011

(In [4841]) Fixes #2458 - Visitor Generator now based on a "piwik access log, combined format" that is replayed faking Time/IP/User Agent/Accept language header. The file can be swapped for any other log file containing requests to piwik.php

The current log file generates a little bit of ecommerce activity, as well as various pages & custom variables (based off Forum.piwik.org log file)

@mattab mattab added this to the 1.5 - Piwik 1.5 milestone Jul 8, 2014
@mattab mattab self-assigned this Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Development

No branches or pull requests

1 participant