App Engine Update - now 150€ billing per month

[dlackner]

Dear Google Community,

we updated our app engine for the server side tracking as we got an error in GTM that our server are not up-to-date. As we did this the price for the app engine went from some cents to 150€/month!!! o.O

The only indication I have so far is that it seems all projects which are affected from this fail are once which are on 'production' Version.

All projects on the 'testing' Version are currently not affected

Is anyone having the same issues? Or knows how to solve this problem?

Best regards
David

[NoCommandLine · Accepted solution]

1) I suspect that your 'production' version is your default service and is receiving all traffic from end users while the 'testing' version is 'internal' and only receives traffic when someone specifically navigates to it and this is few and far in between.

Your default service is thus receiving majority of your traffic and thus uses more resources which in turn leads to a higher bill than the 'testing' version

2) Regarding the jump in your bill, you should take a look at your billing breakdown
    a) Go to console.cloud.google.com/billing
    b) Select your Project
    c) Under the Billing Account Overview tab, select 'Current Month' and click on 'View Report'. 

     You should see a breakdown of the costs (by service/component) that you've incurred for the current month. Going through the breakdown will tell you what is costing you the most. Most likely one of your changes has led to an increased consumption in a service

You can also view the same report for previous months by selecting from the filter on the right hand side of the page


 

..... NoCommandLine ......

 https://nocommandline.com

A GUI for Google App Engine

[dlackner]

yes, the 'production' service was the default which caused so much money

thanks for your help!

Do you also maybe know when it is useful to pay the 'production' service? Or is there any recommendations from Google that you know?

Appreciate your expertise!

Best regards
David

[NoCommandLine]

> Do you also maybe know when it is useful to pay the 'production' service?

Unfortunately, I'm not clear on what you're asking. Can you rephrase your question or provide more explanation/context?

..... NoCommandLine ......

 https://nocommandline.com

A GUI for Google App Engine

[dlackner]

sure, so currently we are running all the things in 'testing' version on the AppEngine. When should we consider to upgrade to the 'production' version?
And what is the main difference between 'production' and 'testing'? Is it that 'production' is just for more traffic, or what is the difference?

Hope this makes it clearer 🙂

[NoCommandLine]

- Version names are typically specified by the project owner (every service has a default version; if you don't specify a name for a version, Google will generate one [see reference]; Google usually generates a version name based on the deployment date). Your team just happened to call yours 'production' and 'testing'. You can call it whatever name you like. Versions allow you to have 'different' flavors of your app under same project (think of it as having different environments where you run your App) 

- I would assume they use 'testing' for when they make or are making changes to the code. To 'test' the changes without affecting production, they deploy to the 'testing' version and can access it at testing-dot-<projectid>.appspot.com

When they're satisfied with their changes, they deploy to 'production' version which is what external users use (it's the default version and is what is served when someone types in <projectid>.appspot.com or whatever is your custom url.

..... NoCommandLine ......

 https://nocommandline.com

A GUI for Google App Engine