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

Bad metrics collection #784

Closed
duker33 opened this issue Mar 20, 2019 · 6 comments
Closed

Bad metrics collection #784

duker33 opened this issue Mar 20, 2019 · 6 comments
Assignees
Labels
2 hours some big and monolith issue with hard decisions, discussions or bug with strong research Metrics feature about business metrics

Comments

@duker33
Copy link
Contributor

duker33 commented Mar 20, 2019

Calculated month grouped orders count from DB with this gist
For every month it's two times much, then Ya.Metrics collected (Ya.Metrics data collected PO).

Metrics is systematically wrong collected. Here we should propose a method to define where problem origins from. And maybe provide some direction to solve this problem.

The task will be implemented with research and chat discussion. It'll be resolved when we'll find a method to prove the problem's source and a direction to solve it.

@duker33 duker33 added 2 hours some big and monolith issue with hard decisions, discussions or bug with strong research discuss issue needs to finish discussion before start working labels Mar 20, 2019
@duker33 duker33 added the Metrics feature about business metrics label Mar 20, 2019
@ArtemijRodionov
Copy link
Contributor

We should exclude yandex orders from the result, because we didn't collect metrics for them until this.

@duker33
Copy link
Contributor Author

duker33 commented Apr 10, 2019

compared orders count at the DB and at the metrics at the [01.04-10.04] time interval:

source orders count
db 275
Ya.Ecommerce 238
Ya.Aim "Купить общая" 253

Seems metrics is not precise yet. But it's still unclear if problem is in adblocks or in smth else

@duker33
Copy link
Contributor Author

duker33 commented Apr 10, 2019

sentry says, that we are still having problems with ya.counter. But it affects only ~3% of users.
As we saw at the previous comment, we lost ~20% of orders.

So the main problem is not in the missed counter.
I propose this decision:

  • we create separated task for sentry issue from the link above. Seems it's about async behavior error
  • we send "Купить общая" aim event not only to Ya.Metrica, but to our backend too. It'll help us to define if it's problem in our js or Ya.Metrica servs side

@duker33
Copy link
Contributor Author

duker33 commented Apr 10, 2019

@artemiy312 , what do you think about poins in the comment above?

If it's ok, i'll create this tasks and close this one

@ArtemijRodionov
Copy link
Contributor

@duker33

we create separated task for sentry issue from the link above. Seems it's about async behavior error

probably it is, we should try the same trick as we did with google analytics

we send "Купить общая" aim event not only to Ya.Metrica, but to our backend too. It'll help us to define if it's problem in our js or Ya.Metrica servs side

let's defer this one until we solve the issue above. Probably it would be enough

@duker33
Copy link
Contributor Author

duker33 commented Apr 15, 2019

@artemiy312 , created #814 and assigned it to you. Hope you don't mind.
We finished this task. If problem stays, we'll create a new one or reopen this one with increased estimate.

@duker33 duker33 closed this as completed Apr 15, 2019
@duker33 duker33 removed the discuss issue needs to finish discussion before start working label Apr 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 hours some big and monolith issue with hard decisions, discussions or bug with strong research Metrics feature about business metrics
Projects
None yet
Development

No branches or pull requests

2 participants