[google-appengine] Re: pycrypto 2.6.1 errors

[Mark Cummins]

>
> @Mark: I'm a little bit confused since I don't think you can set the SDK 
> version used by the app in production. Rather, it is always auto-upgraded 
> to the latest.
>

Ah, no, I mean that we reverted to the old PyCrypto version, rather than 
the SDK version.

Thank you very much for the workaround.

Best,
Mak

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c8bfa883-a325-4332-8278-1b8c9ee7e8f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: pycrypto 2.6.1 errors

[Mark Cummins]

We see this issue in production. It happens whenever we import pycrypto. We 
couldn't find any solution, so we've reverted to the old version on the 
assumption that this is an SDK problem.

On Tuesday, 20 December 2016 21:54:20 UTC, Nick (Cloud Platform Support) 
wrote:
>
> Hey Mark,
>
> Any update on my last questions? Did you make a post to the Public Issue 
> Tracker or would you like to keep corresponding here?
>
> Cheers,
>
> Nick
> Cloud Platform Community Support
>
> On Tuesday, December 6, 2016 at 6:41:40 AM UTC-5, Mark Cummins wrote:
>>
>> The new Python SDK (1.9.49) includes pycrypto update to 2.6.1.
>>
>> We've flipped over to the new library version, and we're now seeing 
>> errors like this:
>>
>>
>> 11:28:31.524/base/data/home/runtimes/python27/python27_lib/versions/third_party/pycrypto-2.6.1/Crypto/Util/number.py:57:
>>  
>> PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using 
>> libgmp >= 5 to avoid timing attack vulnerability.
>> 11:28:31.524 _warn("Not using mpz_powm_sec. You should rebuild using 
>> libgmp >= 5 to avoid timing attack vulnerability.", PowmInsecureWarning)
>>
>>
>> It looks like this is a platform problem with the new 1.9.49 SDK? Or are 
>> we doing something to cause this?
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/691c8292-7bfe-4d82-8004-2835ccfd2528%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Debugging Datastore Read usage

[Mark Cummins]

Aha! Very useful, thanks!

On Monday, 12 December 2016 23:01:28 UTC, Alex (Cloud Platform Support) 
wrote:
>
> Hi Mark,
>
> As another option, Google Stackdriver Monitoring 
>  allows you to retrieve 
> relevant metrics about your Datastore operations. Among the available 
> metrics listed here 
> , you may 
> be interested by the “api/request_count” metric that allows you to retrieve 
> the number of datastore requests within a timeframe as narrow as an hour. 
> You can test this feature on the Metrics Explorer 
>  directly 
> after enabling it. Still, be aware that the number of requests to the 
> datastore may not be representative of the actual number of read calls 
> involved in these requests.
>
> Let me know if that helps you in identifying the periods of your spikes.
>
> Cheers,
> Alex
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f4910f16-435c-4933-b7cd-c61243455ed7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Debugging Datastore Read usage

[Mark Cummins]

Hi,

One day last week our Datastore Read Operations were 5x their normal level, 
and we're trying to identify why.

The problem is almost certainly caused by some corner case in our own code. 
My question is, how can we go about identifying what caused this issue?

As far as I can see, our only way to keep track of Datastore Reads is via 
the billing page ("View Usage History"), which shows the total number of 
reads on a given day (and there is about a 2 day delay before the report is 
ready). Is there any way we can get more precise information about what 
caused our spike in Datastore Reads? If we could narrow it down to a 
particular handler, or even a particular time of day, we could sort it out 
pretty quickly. The main dashboard at least gives you a graph of memcache 
usage by time of day, but nothing for Datastore Reads that I can see?

Thanks,
Mark

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/f54d0305-3e18-4194-aefb-101df7602286%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] pycrypto 2.6.1 errors

[Mark Cummins]

The new Python SDK (1.9.49) includes pycrypto update to 2.6.1.

We've flipped over to the new library version, and we're now seeing errors 
like this:


11:28:31.524/base/data/home/runtimes/python27/python27_lib/versions/third_party/pycrypto-2.6.1/Crypto/Util/number.py:57:
 
PowmInsecureWarning: Not using mpz_powm_sec. You should rebuild using 
libgmp >= 5 to avoid timing attack vulnerability.
11:28:31.524 _warn("Not using mpz_powm_sec. You should rebuild using libgmp 
>= 5 to avoid timing attack vulnerability.", PowmInsecureWarning)


It looks like this is a platform problem with the new 1.9.49 SDK? Or are we 
doing something to cause this?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c8c461ba-eee0-4ea1-a737-5d7fc59207c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] log quota

[Mark Cummins]

Could anyone clarify the pricing? The message says "Please upgrade to the 
Premium Tier", however, when I click "Learn More", there is an option:

Basic Tier
Logs allotment:  5 GB per month per project
Logs allotment overage: $0.50 per GB

https://cloud.google.com/stackdriver/pricing?hl=en_US&_ga=1.212419412.1363903900.1467732610

Our current usage is about 9GB per month. So does this mean we can just pay 
$2 per month for the extra 4GB? 

Or are we forced to use Premium for some reason? The Premium Tier pricing 
is pretty mysterious to me.



On Friday, 25 November 2016 09:03:10 UTC, Marcel Manz wrote:
>
> 100% ACK
>
> This is wrong move by Google to discard any application logs as soon as 
> the 5GB are reached until quota reset, forcing customer to buy Stackdriver 
> Premium in order to keep the existing functionality.
>
> Google should better apply the rule to just show the most recent 5GB of 
> logs (no matter from which source they got ingested from).
>
> Marcel
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/05175268-1f70-4e52-9297-25f26086a776%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[Mark Cummins]

@Kaan Soral. Yes, we also heavily use the images service, it's invaluable 
and we love it. We were also using mail, although it really wasn't a big 
problem to move to an external service. (Though incoming is indeed more of 
an issue) By exotic, I mean things like Prospective Search and 
 XMPP/Channels. I don't think too many people were really affected by those 
deprecations.

On Friday, 25 November 2016 13:38:16 UTC, Kaan Soral wrote:
>
> It is what I meant, apologies if I was confusing
>
> On Friday, November 25, 2016 at 3:36:14 PM UTC+2, George Bittmann wrote:
>>
>> Where is the mail deprecation? Post a link if it's happening please. I 
>> thought they were only no longer approving requests to expand beyond the 
>> 100 daily limit. Is that what you mean?
>>
>>
>> On Thursday, November 24, 2016 at 8:06:33 AM UTC-5, Kaan Soral wrote:
>>>
>>> Hi
>>>
>>> Thanks a lot for the reply again
>>>
>>> For images, https://cloud.google.com/appengine/docs/python/images/ - 
>>> the 1600 resize limit started to age a bit, I'm using the images service 
>>> heavily on https://geobird.com - and considering the recent 4K, 5K 
>>> resolutions, even bumping the limit to 2400 would improve dynamics a lot, 
>>> considering it would at least cover 1080p (Current solution is to just 
>>> serve images with "=s0" - considering most devices have retina resolutions 
>>> now, most images started becoming "=s0" - and a significant bandwidth is 
>>> wasted for clients)
>>>
>>> If we analyse the case for the images service, it provides dynamic 
>>> resizing at instant availability, It's an invaluable service, I love 
>>> appengine because it provides building blocks like these - Instead of 
>>> depreciating such services, it would be lovely to see new ones, for 
>>> example, a "videos" service, even though I'm using Zencoder for video 
>>> processing, if we compare it to the ease of using the images service, it's 
>>> a heavy burden
>>>
>>> @Mark Cummins, I don't know what service you are calling exotic and 
>>> less-used, It would be great if you could provide concrete examples, 
>>> interacting with other app engine users, you would be amazed how each 
>>> component is utilised and valued
>>> If we analyse the case for mail, I personally was using it to send 
>>> mails, so, while the deprecation was an extreme nuisance, it wasn't the end 
>>> of the world, yet, communicating with others, I saw that some were using 
>>> apps as turnkey solutions, or, they were deploying singular apps for their 
>>> clients, so having a practical mail solution was crucial to them, some were 
>>> handling incoming email, while things were simple from the outgoing email 
>>> perspective, for an app that handled both incoming/outgoing email, the 
>>> deprecation was much more worrying
>>>
>>> On Wednesday, November 23, 2016 at 3:28:07 AM UTC+2, Lorne Kligerman 
>>> wrote:
>>>>
>>>> Heard loud and clear on action speaking louder than words.  We have a 
>>>> lot brewing and are excited to show it off when ready.
>>>>
>>>> There have been some deprecation announcements lately.  The objective 
>>>> here is to bring App Engine in line with the rest of GCP.  This is a 
>>>> challenging effort because of how long App Engine pre-dates the rest of 
>>>> the 
>>>> system.  That being said, we do have our users best interests at heart and 
>>>> we believe the future state will be a good one.  Significant improvements 
>>>> have been made to the App Engine Admin API, which officially went GA 
>>>> <https://cloudplatform.googleblog.com/2016/08/automate-deployments-and-traffic-splitting-with-the-App-Engine-Admin-API.html>
>>>>  
>>>> a couple months ago.
>>>>
>>>> Regarding mail, we are currently gathering requirements for a GCP wide 
>>>> solution.  For images, could you give more detail on exactly which limit 
>>>> you're running up against and the scenario?
>>>>
>>>>
>>>> On Tue, Nov 22, 2016 at 2:45 PM, 'Alex (Cloud Platform Support)' via 
>>>> Google App Engine  wrote:
>>>>
>>>>> Hi Kaan,
>>>>>
>>>>> On a side note, it is possible to receive regular emails from the 
>>>>> Google Cloud Platform by following these steps:
>>>>>
>>>

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[Mark Cummins]

Thank you for this update, very reassuring and makes me very happy! 
Personally I'm not too worried about some of the more exotic and less-used 
services being deprecated, so long as their are reasonable migration paths 
and the overall platform remains available.


On Wednesday, 23 November 2016 01:28:07 UTC, Lorne Kligerman wrote:
>
> Heard loud and clear on action speaking louder than words.  We have a lot 
> brewing and are excited to show it off when ready.
>
> There have been some deprecation announcements lately.  The objective here 
> is to bring App Engine in line with the rest of GCP.  This is a challenging 
> effort because of how long App Engine pre-dates the rest of the system.  
> That being said, we do have our users best interests at heart and we 
> believe the future state will be a good one.  Significant improvements have 
> been made to the App Engine Admin API, which officially went GA 
> 
>  
> a couple months ago.
>
> Regarding mail, we are currently gathering requirements for a GCP wide 
> solution.  For images, could you give more detail on exactly which limit 
> you're running up against and the scenario?
>
>
> On Tue, Nov 22, 2016 at 2:45 PM, 'Alex (Cloud Platform Support)' via 
> Google App Engine > wrote:
>
>> Hi Kaan,
>>
>> On a side note, it is possible to receive regular emails from the Google 
>> Cloud Platform by following these steps:
>>
>>1. Access the Cloud Platform Console
>>
>>2. Click the “3 vertical dots” on the top-right section of the menu
>>
>>3. Navigate to preferences->Updates & Offers
>>
>>4. Set email to “On” for Feature announcements
>>
>> By doing this, you will receive emails about the latest feature 
>> announcements on the Cloud Platform.
>>
>> Cheers,
>>
>> Alex
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "Google App Engine" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/google-appengine/EFLhIU9GqjU/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to 
>> google-appengi...@googlegroups.com .
>> To post to this group, send email to google-a...@googlegroups.com 
>> .
>> Visit this group at https://groups.google.com/group/google-appengine.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-appengine/c37962f7-c400-44d9-9ab8-dfd3edc7ec1f%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/20f24616-c354-4703-ac21-5cfa45c563bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Backing up AppEngine

[Mark Cummins]

We use the old crusty Datastire Admin backup tool. We run it nightly from a 
cron. We backup most important entity types nightly, and some less important 
types weekly. We have tested disaster recovery, and it all seems to work fine

We do this to defend against programmer error or attack, e.g. If some 
programmatic process were to delete or mangle our whole Datastore.

The major downside of this aporozch is that is is insanely expensive. We have 
to read every Datastore instance every day, which takes a lot of Read and a lot 
of Instance Hours. For a modest sized datastore this costs us several hundred 
dollars per month. I really wish there was a better approach 

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/61f4cdf8-0370-4d49-abe8-e3e46dab9589%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Google has fixed 30 of 707 bugs reported in the past 12 months

[Mark Cummins]

I also am beginning to fear a "GAE deprecation email". Could anyone at Google 
give any reassurance on this? Is GAE standard going to be abandoned in favour 
of managed VMs (which are actually very different)?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/968b8341-6968-4494-be2d-f8750b9a826a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Are pending_ms still reported in the logs?

[Mark Cummins]

Ah, makes sense. Thanks!

On 28 Jul 2016 10:58 p.m., "'Nick (Cloud Platform Support)' via Google App
Engine"  wrote:

> Hey Mark,
>
> The data will only appear if the request spent time in a pending queue, as
> described in the documentation
> <https://cloud.google.com/appengine/docs/python/logs/> (ctrl+f "Pending
> queue"). So, if it's not there, you can interpret that as pending_ms=0
>
> Cheers!
>
> Nick
> Cloud Platform Community Support
>
> On Tuesday, July 19, 2016 at 1:13:21 PM UTC-4, Mark Cummins wrote:
>>
>>
>> Is the "pending_ms" metric still reported in the logs? I see it mentioned
>> in various places (e.g. here:
>> http://bjk5.com/post/40833194761/pending-queues-and-loading-requests-on-app-engine
>> )
>>
>> We're trying to debug some latency issues and this seems like a useful
>> metic to examin. However, I can't seem to see it in our logs. Has it been
>> removed? Am I missing it somehow?
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Google App Engine" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-appengine/8mHxjsSCOYc/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/f8059d99-428b-4d99-bf7e-83e417b3aea2%40googlegroups.com
> <https://groups.google.com/d/msgid/google-appengine/f8059d99-428b-4d99-bf7e-83e417b3aea2%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CAJuuHwo1Rr7oApb%3Dem3vmhOYqtQJMNR4ztpP3kunoprFAXq%3DKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Are pending_ms still reported in the logs?

[Mark Cummins]

Is the "pending_ms" metric still reported in the logs? I see it mentioned 
in various places (e.g. here: 
http://bjk5.com/post/40833194761/pending-queues-and-loading-requests-on-app-engine)

We're trying to debug some latency issues and this seems like a useful 
metic to examin. However, I can't seem to see it in our logs. Has it been 
removed? Am I missing it somehow?

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/bb1cbbfc-9159-4cdd-a6d7-67f577fbdc5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: GAE Latency & Instance issues

[Mark Cummins]

Thank you so much for this! We also got bitten hard by this problem 
seemingly out of nowhere in the last few weeks. The same request latency 
varying from 200ms to over 10,000ms in some cases, with no obvious reason 
except mysterious gaps in the traces. It's a hard one to debug - there's no 
obvious way to tell that the instances are being CPU starved.

On Thursday, 30 June 2016 08:45:10 UTC+1, Trevor wrote:
>
> Hello ladies and gentlemen, I am here to hopefully draw on some collective 
> knowledge about App Engine and its intricacies. 
>
> For the last two weeks our (my company) site has been experiencing very 
> odd latency issues, and having now tried about 7 different methods of 
> solving it, we are left at exactly where we began: Rising costs with 
> performance that is much lower than previously. 
>
>
> 
>
>
> Essentially what happens is that say 50-60% of our requests are served 
> normally, however the remainder have these extremely long "pauses" in the 
> middle of the trace which is basically during the "processing" phase of the 
> backend handling (after the datastore & memcache data has been retrieved). 
> Here is an example of a single page that in the space of an hour had wildly 
> different loading times for users. The vast majority were the same thing, 
> grab 3 things from memcache and spit out the html retrieved from memcache. 
> That's it... 
>
>
> 
>
> And some individual traces to see what is happening
>
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>
>
>
> So essentially the troubleshooting steps we took to figure out what was 
> going wrong. 
>
>- Checked all deployed code over the week preceding and following the 
>latency spike to ensure we hadn't let some truly horrendous, heavy code 
>slip through the review process. Everything deployed around that period 
> was 
>rather light, backend/cms based updates, hardly anything touching 
>customer-facing requests. 
>- Appstats, obviously. On the development server (and even unloaded 
>test versions on the production server) such behavior is not seen. Didn't 
>help. 
>- Reducing unnecessary requests (figure 1) - We noticed some of our 
>ajax-loaded content was creating 2-3 additional, separate requests per 
>user-page-load, and as such refactored the code to only call those things 
>when absolutely necessary, and eliminated one altogether. For the most 
>part, a page load now equals one request. This had no effect on the 
> latency 
>spikes
>- Created a separate system that meant that our backend task-based 
>processing was cut down by 90%, and thus the instance average load was 
>reduced significantly. This had the opposite effect and average latency 
>actually climbed, I suspect because of the extensive memcache use with 
>large chunks of data (tracking what things should be updated by the 
> backend 
>tasks)
>- Separated the front end and tasks-back-end into modules/services so 
>that frontend requests could have 100% instance attention. This had a 
> small 
>effect, but the spikes are still regularly happening (as seen in the above 
>traces). 
>- Played with max_idle_instances  - This had a wonderful effect of 
>*halving* our daily instance costs, with almost no effect on latency. 
>When this is set to automatic, we get charged for a huge amount of unused 
>instances, it actually borders on ludicrous (figure 2) 
>- Played with max_concurrent_requests (8->16->10) which only served to 
>make the latency issues worse. 
>- Hours and hours pouring over logs, traces, dashboard graphs. 
>
>
> * Figure 1 (Since the latency spike on June 5th, we have worked to reduce 
> meaningless requests through API calls or task queuing) *
>
>
> 
>
> *Figure 2 (14:40 is when the auto-scaling setting was deployed)*
>
>
> 
>
> What I have noticed is when the CPU cycles spike, *so d

[google-appengine] Usability of new logs viewer

[Mark Cummins]

The old App Engine console is gone (sadness). The new logs viewer has 
improved a lot, but it's still frustrating compared to the old viewer.

Here are a few things which really bug me, I wonder if anyone has come up 
with work-arounds or solutions:

1) Collapse the metadata block [part in curly braces]
In the expanded view, every log shows the expanded metadata block in curly 
braces first. This consumes massive chunks of my screen real estate, while 
containing information that is mostly irrelevant most of the time. I'd like 
this block to be collapsed, so I can just see the info/warning/error 
messages that contain the useful information most of the time. That would 
allow me to much more quickly browse the logs and see useful information.

2) Disable auto-update on scroll
Generally I want to work with a block of logs for a while when diagnosing a 
problem. I find the auto-refresh on scroll unhelpful. As I scroll around 
new logs get loaded and it's easy to lose my place. The old paged view was 
much more practical. Is there a way to disable this?

Hopefully some people have work arounds, I really feel like I have no idea 
what's going on in my app any more now that we're forced to use the new 
viewer. Small UI differences have a big impact on usability. Colour scheme 
is also bad, but I have no hope of Google improving that.

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/99ea67ca-828c-4246-b69c-524f3e9b9f62%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] New Cloud Console

[Mark Cummins]

+1 for the speed of the new console. The old console is very noticeably 
faster.

On Thursday, 25 February 2016 01:58:58 UTC, Christian F. Howes wrote:
>
> Hi Lorne,
>
> Is there any chance that you can share the console roadmap with us?  given 
> that we are getting the turn-down threats again, and the new console is 
> still missing many features it would be helpful to know which ones are 
> known to the team working on the console and which need new tickets.
>
> Is overall speed of the new console going to be addressed?  I lose several 
> developer hours a week using the new console waiting for things to load, 
> and as such my team and I tend to use the old console whenever possible.
>
> Thanks,
>
> Christian
>
> On Tuesday, February 23, 2016 at 4:43:55 PM UTC-8, Lorne Kligerman wrote:
>>
>> I'm happy to report that both features are in the works and will launch 
>> shortly, before the old console is turned down.
>>
>> Cheers,
>> Lorne.
>>
>>
>> On Tuesday, February 23, 2016 at 3:52:19 PM UTC-8, PK wrote:
>>>
>>> We also need the “Billing/Usage History” equivalent functionality, has 
>>> this page been migrated to the new console?
>>>
>>> PK
>>> p...@gae123.com
>>>
>>>
>>>
>>>
>>> On Feb 23, 2016, at 3:46 PM, johnP  wrote:
>>>
>>> Just got email that old appengine console will be shut off in 6 weeks. 
>>>  The new cloud console does not have a "migrate traffic" option in the 
>>> Versions screen.  This was my absolute favorite new feature in a long, long 
>>> time.  Will it be available in the new console?
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Google App Engine" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to google-appengi...@googlegroups.com.
>>> To post to this group, send email to google-a...@googlegroups.com.
>>> Visit this group at https://groups.google.com/group/google-appengine.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/google-appengine/540d27f2-1841-4be8-a21b-17aea883dd84%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/29df1e42-69fb-40c6-a953-be6fbc94cd3c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: New Cloud Console

[Mark Cummins]

Will the logs viewer in the Cloud Console be improved before the App Engine 
console is shut down? The main reason I still use the old console is that I 
find the old logs viewer much more useful than the new one.

The new logs viewer is shows a view that is either totally collapsed 
(useless) or totally expanded (so verbose it's hard to see anything). The 
setup of the old viewer was ideal. (Semi-expanded, no headers, but showing 
one line of each log message in a request). It's really hard to get a quick 
sense of what's happening in the logs with the new viewer.

It has a number of other downsides, but I could mostly live with it if this 
basic usability issue was fixed.

On Tuesday, 23 February 2016 23:46:19 UTC, johnP wrote:
>
> Just got email that old appengine console will be shut off in 6 weeks. 
>  The new cloud console does not have a "migrate traffic" option in the 
> Versions screen.  This was my absolute favorite new feature in a long, long 
> time.  Will it be available in the new console?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/af6c754e-81d2-4655-86c7-0a7f056f5e04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: App Engine admin console redirects to Developers Console

[Mark Cummins]

The new logs viewer is much less usable. Because it's either totally 
collapsed or totally expanded, it's much much harder to extract meaningful 
patterns of events at a glance. I would really like to get back the 
single-line-per-message view that the old viewer had.
Also, it seems slower to display first logs. 

On Wednesday, 7 October 2015 11:01:20 UTC+1, Stewart Fife wrote:
>
> Hello! 
>
> We are pleased to announce that we redirected the first set of App Engine 
> admin console menus to Developers Console today. This begins the final 
> stage of consolidating the management of Google Cloud Platform services 
> into one consistent experience for customers. 
>
> Thanks for all your feedback on this important change. 
>
> Stewart on behalf of the GAE team

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/2695feba-d2b7-4ee1-abde-c2d6f1198fcd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Where is the Datastore Admin in the new Developers Console?

[Mark Cummins]

Actually, I just discovered it is available in the new  Developers Console, 
thought it's in a very non-obvious place. It's in

Cloud Datastore > Settings > Open Datastore Admin

Similarly, I thought Cron Jobs were gone, but they're just weirdly hidden 
in a tab in the Task Queues view.




On Wednesday, 7 October 2015 11:35:48 UTC+1, Oliver Urs Lenz wrote:
>
> Thanks very much for your solution! I am quite exasperated as to how 
> Google doesn't seem to care about usability.
>
> On Wednesday, October 7, 2015 at 11:50:41 AM UTC+2, Mark Cummins wrote:
>>
>> Quick workaround I found. If you look at the greyed-out link you'll see 
>> the URL has an '&deprecated' parameter. If you remove that you can still 
>> get to all of the greyed out links, at least for now.
>>
>> I hope Google isn't just going to dump this functionality. We rely 
>> on Datastore Admin to manage our backups. We also use the bulk entity 
>> delete quite often. As far as I can see neither of these are possible in 
>> the new Developers Console.
>> In general, to be honest I also just find the old Developers Console much 
>> more pleasant to use.
>>
>>
>> On Wednesday, 7 October 2015 10:36:57 UTC+1, Oliver Urs Lenz wrote:
>>>
>>> As of today, the Datastore Admin (along with a lot of other menu 
>>> options) in the old App Engine console is greyed out and struck strough, 
>>> with a tool tip saying "This feature has moved to the new Developers 
>>> Console". But clicking on it leads to me to the Datastore Dashboard, no 
>>> Datastore Admin appears to be available in the Developers Console.
>>>
>>> Am I overlooking the Datastore Admin in the Developers Console, and if 
>>> so, where is it located? (I need the Datastore Admin to see whether backups 
>>> completed succesfully and what string of characters was assigned to them.)
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/ab313576-3925-4c74-bb23-1f9a727385d1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: App Engine admin console redirects to Developers Console

[Mark Cummins]

Could you give feedback on what happened to the Datastore Admin page? This 
seems to be gone, and we rely on it to manage our backups and also use it 
perform bulk deletes.

On Wednesday, 7 October 2015 11:01:20 UTC+1, Stewart Fife wrote:
>
> Hello! 
>
> We are pleased to announce that we redirected the first set of App Engine 
> admin console menus to Developers Console today. This begins the final 
> stage of consolidating the management of Google Cloud Platform services 
> into one consistent experience for customers. 
>
> Thanks for all your feedback on this important change. 
>
> Stewart on behalf of the GAE team

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/8e15b607-c8a1-4fb7-aee0-b7c48c2b2422%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Where is the Datastore Admin in the new Developers Console?

[Mark Cummins]

Quick workaround I found. If you look at the greyed-out link you'll see the 
URL has an '&deprecated' parameter. If you remove that you can still get to 
all of the greyed out links, at least for now.

I hope Google isn't just going to dump this functionality. We rely 
on Datastore Admin to manage our backups. We also use the bulk entity 
delete quite often. As far as I can see neither of these are possible in 
the new Developers Console.
In general, to be honest I also just find the old Developers Console much 
more pleasant to use.


On Wednesday, 7 October 2015 10:36:57 UTC+1, Oliver Urs Lenz wrote:
>
> As of today, the Datastore Admin (along with a lot of other menu options) 
> in the old App Engine console is greyed out and struck strough, with a tool 
> tip saying "This feature has moved to the new Developers Console". But 
> clicking on it leads to me to the Datastore Dashboard, no Datastore Admin 
> appears to be available in the Developers Console.
>
> Am I overlooking the Datastore Admin in the Developers Console, and if so, 
> where is it located? (I need the Datastore Admin to see whether backups 
> completed succesfully and what string of characters was assigned to them.)
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/c7f18e76-83ba-4e7c-af23-7a6f24e74d53%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: Announcing a credit for App Engine applications with new custom domains

[Mark Cummins]

Hi Andrew,

Nice to hear that naked domains are now supported too. Given a free choice, 
is there any reason to prefer www.example.com over example.com? I'm new to 
the issue and just noticed some other providers advise against naked 
domains for scalability reasons: 
e.g.: https://devcenter.heroku.com/articles/apex-domains

Or is this not a concern on App Engine?

Thanks,
Mark

On Monday, 14 April 2014 22:18:44 UTC+10, Andrew Jessup wrote:
>
> Hi Igor - actually we do. See Step 2 in under App Engine > Settings > 
> Custom Domains
>
>
> On Mon, Apr 14, 2014 at 5:21 AM, Igor Kharin  > wrote:
>
>> Hello Andrew,
>>
>> I believe you've mistakenly closed an issue unrelated to this one -- issue 
>> #777 . 
>> I've checked the new UI and it doesn't seem like you guys support naked 
>> domains just yet.
>>
>>
>> On Sat, Apr 12, 2014 at 6:31 AM, Andrew Jessup > > wrote:
>>
>>> Hi Everyone,
>>>
>>> I'm happy to report that we have just added support for mapping custom 
>>> domains to an App Engine application directly from within the Google 
>>> Developers Console (https://console.developers.google.com/). This means 
>>> that you can associate your domains without being required to purchase 
>>> Google Apps for each domain first.
>>>
>>> This isn't dependent on our recently released Cloud DNS service - 
>>> although if you *are* looking for a great DNS, they do go well together 
>>> :)
>>>
>>> There are still some features we're looking to add to this - notably, 
>>> support for SSL for custom domains (which is still available if you use 
>>> Google Apps to associate a domain, and is available automattically from 
>>> your *.appspot.com URLs). In the meantime, we hope you find this to be 
>>> a more effective and simpler way to set up your App Engine apps.
>>>
>>> Since Google Apps is no longer necessary, from today we are no longer 
>>> offering the Jump Start credit to new applicants. Those who have already 
>>> been awarded the credit will still be able to draw down from any unused 
>>> credit on their account, and if you have recently applied prior to today 
>>> then we will still review your application. However new applications will 
>>> not be accepted.
>>>
>>> Thanks for your patience.
>>>
>>> Regards,
>>>
>>> Andrew
>>> Product Manager, Google Cloud Platform
>>>
>>> On Thursday, 27 March 2014 20:39:24 UTC+1, Vinny P wrote:

 On Thu, Mar 27, 2014 at 2:26 PM, Barry Hunter 
  wrote:

 Can't just use cloud-dns to CNAME your domain to ghs.googlehosted.com
>  - *without *using Google Apps, because still needs to know the 
> domain-to-appid mapping. 
>
> So can use Cloud-DNS, but still need Google Apps *too*. 
>


 I agree with Barry. I read through the Cloud DNS documentation, but 
 unless I missed something, I don't see a way to associate domains with 
 specific applications. 

 For instance, I can create a managed zone and associate it with a 
 project by calling this REST command: https://developers.google.com/
 cloud-dns/api/v1beta1/managedZones/create . But where is the 
 association between domain/project to App Engine ID?
   
  
 -
 -Vinny P
 Technology & Media Advisor
 Chicago, IL

 App Engine Code Samples: http://www.learntogoogleit.com
   

>>>  -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Google App Engine" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to google-appengi...@googlegroups.com .
>>> To post to this group, send email to google-a...@googlegroups.com 
>>> .
>>> Visit this group at http://groups.google.com/group/google-appengine.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Google App Engine" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to google-appengi...@googlegroups.com .
>> To post to this group, send email to google-a...@googlegroups.com 
>> .
>> Visit this group at http://groups.google.com/group/google-appengine.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
>
> Andrew Jessup | Product Manager, Google Cloud Platform | jes...@google.com 
>  
>  

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.