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

Look into reported analytics discrepancies #77

Closed
GUI opened this issue Jul 24, 2014 · 1 comment
Closed

Look into reported analytics discrepancies #77

GUI opened this issue Jul 24, 2014 · 1 comment
Assignees

Comments

@GUI
Copy link
Member

GUI commented Jul 24, 2014

One of our users reported that they new a client made ~194,000 requests on July 22. However, in our view of the analytics, only 24,652 requests were made. Need to investigate what's up. The account ID that reportedly made the requests is 758f2ff8-434e-4d7e-b1e0-af15d4a94f26.

@GUI
Copy link
Member Author

GUI commented Aug 5, 2014

Upon further examination, I was unable to find any logs on our servers that would explain the 170,000 missing requests. According to our logs, there were around 5,000 requests that were indeed missing from our web analytics, due to an edge-case scenario (the requests hit our lower level nginx-based IP rate limits). So while that edge-case does need to be fixed so those properly get logged, I didn't find any record of the other missing 165,000 requests.

Until I hear back more from the user, I'll close this, and open up a new issue specific to the 5k of low-level rate limits errors that didn't show up in the analytics system: #106

@GUI GUI closed this as completed Aug 5, 2014
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