You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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
.The text was updated successfully, but these errors were encountered: