Estimated Cost field is missing in Appengine's new Developer Console - google-app-engine

In the old (non-Ajax) Google Appengine's Developer Console Dashboard - showed estimated cost for the last 'n' hours. This was useful to quickly tell how the App engine is doing vis-a-vis the daily budget.
This field seems to be missing in the new Appengine Developer Console. I have tried to search various tabs on the Console and looked for documentation, but without success.
Looking for any pointers as to how do I get to this information in the new Console and any help/pointers are highly appreciated !

App Engine > Dashboard
This view shows how much you are charged so far during the current billing day, and how many hours you still have until the reset of the day. This is equivalent to what the old console was showing, except there is no "total" line under all charges.
App Engine > Quotas
This view shows how much of each daily quota have been used.
App Engine > Quotas > View Usage History
This view gives you a summary of costs for each of the past 90 days. Clicking on a day gives you a detailed break-down of all charges for that day.

Related

Quota exceeded for quota metric 'Queries' and limit 'Queries per minute per user' of service 'gmail.googleapis.com'

Our application makes use of a service account that has been authorized for the entire domain by the admin. With this service account our application accesses the domain user's emails with Gmail APIs like GetMessage.
All of a sudden, starting this week, we have started receiving the errors intermittently
Quota exceeded for quota metric 'Queries' and limit 'Queries per minute per user' of service 'gmail.googleapis.com' for consumer 'project_number:XYZ
There is no change in our application or frequency at which we access emails. We are using batch size of 10 while using the API.
The 'Quota exceeded errors count (10 sec) - Queries per minute' graph in the GCP dashboard is empty. So we are really not sure what is going on and why we are suddenly hitting the quota limits.
Also, I am not sure how the 'per-user' limit is applied when my app accesses the user mailboxes with the service account. The documentation around this is vague, at least to me.
These errors are really impacting our ability to serve our customers. Moreover not knowing why we are getting these errors is shaking our confidence in the Gmail APIs.
Any help in this regard is highly appreciated.
Thanks
UPDATE:
Today we are seeing lots of
"User-rate limit exceeded. Retry after <timestamp>"
errors. Seems like this time around we are hitting some quota limit other than 'queries per minute'. While I look in my client implementation and figure out why this is happening, feel free to share any recommendations you may have.
Thanks.
Google analytics has limits and quotas on API requests. You can increase it. If you don't want to do it, daily quotas are refreshed at midnight Pacific Standard Time.

Google analytics ADD-ON google spreadsheets : AVG Session duration and Pagesviews/sessions

Im working on a custom google spreadsheet analytics dashboard.
Here's the situation, I'm trying to get specific info:
Sessions, users, pageviews pageviews/sessions, avg session duration, bouncerate and % new sessions.
The thing is I almost have all the right information except for AVG Session duration and Pageviews/sessions.
Here's a screenshot of the problem:
http://puu.sh/i2rGf/37b2dab3fb.png (its the yellow and the pink one)
Google returns the value's in seconds where you easily devide by 86400
well, I've tried that and no result.
Its kinda weird because everyone is talking about a result like 1234.1234
but mine is 1234.1234.1234.1234 ?
Ideas on where the problem might be?
Check the locale in your spreadsheet settings. It needs to be US to match the GA data being sent.

How much AppEngine Instance hours should I expected?

I have just developed a mobile apps which basically for users to upload, download photoes, add, update, search , delete, refresh transaction, and query report. Every action need submit request to Appengine Server.
I am using CloudEndpoint, oAuth2.0 and Objectify to implement this appengine. When I'm testing alone, The instance hours has used up 40% . How much billing for instance can I imagine if 100 people using this app? How does it calculate the instance hours? by request of submitting? or by time of instance working on multiple request??
is it worth?
If my target is more than 100 users to using my apps. Is it worth? Could you please share me what exactly I misunderstood about this instance.
Thanks
As others have commented, the question is very hard to answer. The easiest answer I can think of is by looking at the response header "X-AppEngine-Estimated-CPM-US-Dollars". You have to be a member of the Cloud Platform Project (see the Permissions page in Cloud Platform developers console) to see this header (you can check it in your browser).
The header tells you what the cost of the request was in US Dollars multiplied by 1000.
But think of it as an indication. If your request spawns other processes such as tasks, those costs are not included in the number you see in that header.
The relationship between Frontend instance hours and the number of requests is not linear either. For one, you will be charged a number of minutes (not sure if it's 15 minutes) when the instance spins up. And there are other performance settings that determine how this works.
Your best bet is to run the app for a while against real users and find out what the costs were in a given month or so.

AppEngine application NOT responding even though well within quota limits with credit balance

If I have a credit balance in my Google AppEngine dashboard for a particular Open Data Kit Aggregate instance which is well within its quota limits, why am I getting this message??
"AppEngine Application Problem. A problem has occurred that prevents
your AppEngine application from responding. Your application may have
exceeded its per-minute or daily usage quotas. Please visit your
application dashboard at Google AppEngine. The Billing Status section
will indicate what daily or per-minute usage limits your application
has exceeded...If neither of those indicate any problems, then your application's Logs may; these are reachable from the dashboard via the Logs link on the left sidebar under the Main heading."
I have search the dashboard far and wide and don't see ANY red flags whatsoever relating to logs, or exceeding any quota limits. I added a new credit card and paid a $3 outstanding bill by making a payment for $20. Hence a $17 credit balance. About to give up.
One thing you should definitely do is go to SITE ADMIN -> PREFERENCES and tick "Disable faster background actions"
That is the only reason your quota should be finishing so fast.
Can you give us a screenshot of your logs, particularly datastore read operations, that is usually what spikes over the quota.
If you don't find any issues on your own, post a query on https://groups.google.com/d/forum/opendatakit. They are quite responsive, especially Mitch.

Google App Engine - Can't Update Budget

I have billing enabled on my project, and have even issued a $10 payment just to test out the process (it works). But I am unable to change my daily budget on the google app engine dashboard.
I go to "Billing Status" section.
I am entering the new daily budget and I hit the "submit" button.
I am getting the not very informative error: "There was an error processing the request".
So I'm stuck without being able to update my budget, and my quota has exceeded for instance hours. My users are receiving errors and I am losing money, without any option of reaching out to Official Google Support (tried to email support - it can take up to a couple of days for them to get back to you, and the phone number requires a PIN that only premium customers get. becoming a premium customer also takes a couple of days...).
Any suggestions?
I have already tried:
making sure I have only one Google account signed in while changing the budget
replacing payment method
adding another user as a billing admin and changing the budget with that user
Nothing seems to work.
UPDATE: After reaching out to a developer advocate from Google, I found out that they are aware of this issue. They claim to have solved it last night, and for me the bug is now solved.

Resources