-
Notifications
You must be signed in to change notification settings - Fork 616
Requests made datastore v0.1.1 are shown as v1beta2 requests in API usage graph #1532
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
Comments
Sorry, accidentally submitted before actually writing anything. Must have accidentally hit some secret keyboard shortcut. |
These are my usage graphs: I think I'm using the new package right, but is there anything I need to do to make requests go to v1beta3 or v1? I need to do this before the old API is turned down
|
Any usage of We will have a release soon for v1. The only thing you'll need to do is upgrade As for the usage graphs, I have to assume it's coming from some other Datastore usage, as long as you've been using the versions of our library stated above. If that doesn't explain it, we can ask @pcostell if he has any ideas. |
You're right – I have a service running on one server in my project that still uses the v1beta2 API, and it looks like all the v1beta2 logs are from that one server's IP. I thought that v1beta3 traffic was being counted as v1beta2 traffic because I assumed that there would be some kind of log of API usage for every version. However, there are no logs or data on the usage graph for the other servers making requests to the v1beta3 API. I've entirely removed |
I'm not sure, but @pcostell might have insight into that. Going to close the issue since we're not talking about a bug in our library. Feel free to keep discussing. |
v1beta3 and v1 traffic unfortunately do not appear in the API console usage tracker: googleapis/google-cloud-datastore#133 |
@pcostell Thank you. I'll subscribe to that issue. |
I looked at my API usage in my GCP project and the graph showed that all of my requests to Datastore are made with the v1beta2 API, even though I've migrated some of my servers to v1beta3. Is this a problem with
@google-cloud/datastore
, a backend issue, or something I'm doing wrong?The text was updated successfully, but these errors were encountered: