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.

Sign up for GitHub

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

Jump to bottom

show incoming data which could not be processed #8732

Closed
hpvd opened this issue Sep 8, 2015 · 5 comments
Closed

show incoming data which could not be processed #8732

hpvd opened this issue Sep 8, 2015 · 5 comments
Assignees
@tsteur
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.
Milestone
2.15.0

Comments

@hpvd
Copy link

hpvd commented Sep 8, 2015

If you are working with with lots of actions e.g. events on your site it could happen that you setup something wrong e.g. a needed parameter is missing or...
To find these problems, it would be great, to have a list (log file) were all "not processable" incoming "messages" are stored (logged)

second step: having this list accessible from piwik backend, each user could report this problem to his site admin..

Maybe there is already a way how to get that kind of information, but always when searching for it one simply get informations about using the web-server logs in piwik...
@tsteur
Copy link
Member

tsteur commented Sep 8, 2015

I think this is a duplicate of #7550 Can you confirm @hpvd ?

@hpvd
Copy link
Author

hpvd commented Sep 8, 2015

interesting, hmm maybe it could fit within this. But it should not only work in a special "safe mode" but always.
Reason: there could be some faulty actions/events which are only triggered e.g. twice per month.
Having to have safe mode on on could easily miss them.
Or other way around it must be possible to use this safe mode permanently on live sites without any problems (e.g. performance)
Thinking about this, maybe this should be a general requirement, because one could think of several thinks which would not appear within a short testing period...

@hpvd
Copy link
Author

hpvd commented Sep 8, 2015

I will move these notes to the mentioned tickets...

@tsteur
Copy link
Member

tsteur commented Sep 8, 2015

Yes the solution should work always, in production and fast (not affecting performance)

BTW: There is also #6209

@tsteur
Copy link
Member

tsteur commented Sep 8, 2015

Sweet, I'll close it then for now

@tsteur tsteur closed this as completed Sep 8, 2015
@tsteur tsteur added the duplicate For issues that already existed in our issue tracker and were reported previously. label Sep 8, 2015
@tsteur tsteur added this to the 2.15.0 milestone Sep 8, 2015
@tsteur tsteur self-assigned this Sep 8, 2015
@hpvd hpvd mentioned this issue Sep 8, 2015
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tsteur tsteur

Labels
duplicate For issues that already existed in our issue tracker and were reported previously.
Projects
None yet
Milestone
2.15.0
Development

No branches or pull requests
2 participants
@tsteur @hpvd