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
API Umbrella v0.14 was a rather sizable update, which is why I had been holding off on upgrading our servers until I had more time (although it should be backwards compatible and still easy to upgrade, we just need to be a little careful about the order in which we upgrade things). But it would be good to upgrade, so I'm just adding an issue in here for us to track this.
I was just reminded of this today, since a small analytics update in v0.14 (excluding non-API traffic from the analytics database) would have helped cut down on some of the garbage analytics (159 million requests) one IP address has been generating for the past few months: https://github.com/18F/api.data.gov-ops/commit/590e154e66e8cf57b744db684d9ec8e67fcff74c (I reached out to the user, but never heard back, and since all of the requests from this IP are actually failed requests, blocking the IP seemed fine. I'm also deleting all of these bogus requests from the analytics database, since they're just taking up space and not valuable).
The text was updated successfully, but these errors were encountered:
The one little glitch we ran into is that the public metrics page isn't working after the upgrade: #387 Since this page doesn't get hit a lot and doesn't seem super-critical, I'm going to leave this until tomorrow or after the weekend.
API Umbrella v0.14 was a rather sizable update, which is why I had been holding off on upgrading our servers until I had more time (although it should be backwards compatible and still easy to upgrade, we just need to be a little careful about the order in which we upgrade things). But it would be good to upgrade, so I'm just adding an issue in here for us to track this.
I was just reminded of this today, since a small analytics update in v0.14 (excluding non-API traffic from the analytics database) would have helped cut down on some of the garbage analytics (159 million requests) one IP address has been generating for the past few months: https://github.com/18F/api.data.gov-ops/commit/590e154e66e8cf57b744db684d9ec8e67fcff74c (I reached out to the user, but never heard back, and since all of the requests from this IP are actually failed requests, blocking the IP seemed fine. I'm also deleting all of these bogus requests from the analytics database, since they're just taking up space and not valuable).
The text was updated successfully, but these errors were encountered: