Re: [google-appengine] New Cloud Console

[Joshua Smith]

Exactly.

I will take ugly, fast, and functional over slick and broken any day.

It’s why I use Emacs and not some IDE :)

> On Mar 18, 2016, at 1:16 PM, johnP  wrote:
> 
> In general, it seems like the original console was built by engineers who 
> used app engine and the new console is built with engineers who were told to 
> 'make it better'  but don't use app engine at all.  Some really basic stuff 
> is missing. 

-- 
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/6960480C-EBE5-4FDA-BBAA-1470B03FF0F1%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] New Cloud Console

['Adam (Cloud Platform Support)' via Google App Engine]

Hi Christian,

We've prodded the engineering team to update the issue trackers, so 
hopefully we will see some updates. The exception is Issue 6799 
 which was 
a years old report of slowness which is being closed out due to inactivity. 
Any new issues of that type should be filed as a new issue report.

On Tuesday, March 8, 2016 at 3:29:37 PM UTC-5, Christian F. Howes wrote:
>
> Hi Nick,
>
> Can you just review cloud support case 08706899 for which PIT issues are 
> not properly updated?  I've listed them out there in the original filing of 
> the case and the response from the support team is that several of them are 
> fixed.
>
> Thanks,
>
> Christian
>
> On Monday, March 7, 2016 at 11:15:49 AM UTC-8, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Chris,
>>
>> If you could link which issues those are which have been fixed but not 
>> updated, we could take a look and determine whether they should be updated 
>> with any new relevant information, such as a fix. Feel free to reply to me 
>> in this thread.
>>
>> Best wishes,
>>
>> Nick
>>
>> On Thursday, February 25, 2016 at 1:09:43 PM UTC-5, Christian F. Howes 
>> wrote:
>>>
>>> Thanks Lorne. 
>>>
>>> Will we also be better at triaging and updating the Public Issue 
>>> Tracker?  Paid support told me today that several of the issues I filed 
>>> last year are supposedly fixed, but the Public Issue Tracker has yet to 
>>> be updated. 
>>>
>>> The lack of information provided, but the hard deadline on the turn-down 
>>> notice really concerns me as I don't have confidence that I will be able 
>>> to efficiently and effectively manage my app 6 weeks from now. 
>>>
>>> Thanks, 
>>>
>>> Christian 
>>>
>>> On 2/25/16 04:49, 'Lorne Kligerman' via Google App Engine wrote: 
>>> > Thanks everyone for the feedback.  Overall, we are going to reach 
>>> feature 
>>> > parity in the Cloud Platform Console before turning down the Admin 
>>> Console. 
>>> >   The next communication we send will have more details and will 
>>> outline any 
>>> > gaps that exist and our plans to address them.  To answer the 
>>> questions 
>>> > asked here: 
>>> > 
>>> > - the dispatch rules will not be visible right away, but we are 
>>> actively 
>>> > working on a mechanism for you to view all of your App Engine 
>>> configuration 
>>> > in one place 
>>> > - prohibiting code downloads will not show up in the same way, but 
>>> this can 
>>> > be managed through roles and upcoming IAM functionality 
>>> > - as mentioned already, performance is a known issue that is a top 
>>> priority 
>>> > for the team 
>>> > 
>>> > Please continue to log issues as Nick mentioned and we will triage 
>>> > accordingly. 
>>> > 
>>> > Cheers, 
>>> > Lorne. 
>>> > 
>>> > On Thursday, February 25, 2016 at 6:13:25 AM UTC-5, troberti wrote: 
>>> >> 
>>> >> 1+ for speed. Also, is the requests/seconds coming to the new 
>>> console? At 
>>> >> least for me that's an easier value to discuss. Besides, the new 
>>> console's 
>>> >> request/minute do not match the request/second metric in the old 
>>> console. 
>>> >> 
>>> >> On Thursday, February 25, 2016 at 11:20:34 AM UTC+1, Mark Cummins 
>>> wrote: 
>>> >>> 
>>> >>> +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 

Re: [google-appengine] New Cloud Console

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Christian,

I just noticed that case is still open. Feel free to respond to that case 
if you feel that anything you've brought up there remains unaddressed. For 
my part, I'm looking over the given Public Issue Tracker threads and 
looking into getting a communication out on those threads.

Regards,

Nick 

On Tuesday, March 8, 2016 at 3:29:37 PM UTC-5, Christian F. Howes wrote:
>
> Hi Nick,
>
> Can you just review cloud support case 08706899 for which PIT issues are 
> not properly updated?  I've listed them out there in the original filing of 
> the case and the response from the support team is that several of them are 
> fixed.
>
> Thanks,
>
> Christian
>
> On Monday, March 7, 2016 at 11:15:49 AM UTC-8, Nick (Cloud Platform 
> Support) wrote:
>>
>> Hey Chris,
>>
>> If you could link which issues those are which have been fixed but not 
>> updated, we could take a look and determine whether they should be updated 
>> with any new relevant information, such as a fix. Feel free to reply to me 
>> in this thread.
>>
>> Best wishes,
>>
>> Nick
>>
>> On Thursday, February 25, 2016 at 1:09:43 PM UTC-5, Christian F. Howes 
>> wrote:
>>>
>>> Thanks Lorne. 
>>>
>>> Will we also be better at triaging and updating the Public Issue 
>>> Tracker?  Paid support told me today that several of the issues I filed 
>>> last year are supposedly fixed, but the Public Issue Tracker has yet to 
>>> be updated. 
>>>
>>> The lack of information provided, but the hard deadline on the turn-down 
>>> notice really concerns me as I don't have confidence that I will be able 
>>> to efficiently and effectively manage my app 6 weeks from now. 
>>>
>>> Thanks, 
>>>
>>> Christian 
>>>
>>> On 2/25/16 04:49, 'Lorne Kligerman' via Google App Engine wrote: 
>>> > Thanks everyone for the feedback.  Overall, we are going to reach 
>>> feature 
>>> > parity in the Cloud Platform Console before turning down the Admin 
>>> Console. 
>>> >   The next communication we send will have more details and will 
>>> outline any 
>>> > gaps that exist and our plans to address them.  To answer the 
>>> questions 
>>> > asked here: 
>>> > 
>>> > - the dispatch rules will not be visible right away, but we are 
>>> actively 
>>> > working on a mechanism for you to view all of your App Engine 
>>> configuration 
>>> > in one place 
>>> > - prohibiting code downloads will not show up in the same way, but 
>>> this can 
>>> > be managed through roles and upcoming IAM functionality 
>>> > - as mentioned already, performance is a known issue that is a top 
>>> priority 
>>> > for the team 
>>> > 
>>> > Please continue to log issues as Nick mentioned and we will triage 
>>> > accordingly. 
>>> > 
>>> > Cheers, 
>>> > Lorne. 
>>> > 
>>> > On Thursday, February 25, 2016 at 6:13:25 AM UTC-5, troberti wrote: 
>>> >> 
>>> >> 1+ for speed. Also, is the requests/seconds coming to the new 
>>> console? At 
>>> >> least for me that's an easier value to discuss. Besides, the new 
>>> console's 
>>> >> request/minute do not match the request/second metric in the old 
>>> console. 
>>> >> 
>>> >> On Thursday, February 25, 2016 at 11:20:34 AM UTC+1, Mark Cummins 
>>> wrote: 
>>> >>> 
>>> >>> +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" 

Re: [google-appengine] New Cloud Console

['Ula Krukar' via Google App Engine]

Quick tip for less clicks: If you pin any section you use frequently, you
will get a quick link to it in the left-top corner.

wt., 8.03.2016 o 15:39 użytkownik Christian F. Howes <
christian.ho...@starmakerinteractive.com> napisał:

> Lorne,
>
> First off the link to customer support is buried inside some menu option
> that does not show up in search.
> While never officially supported, the customer support team taught me how
> to link to an individual log record in the old console.  This has really
> helped me both with internal QA and with customer support tickets.
> The links to individual datastore records and query results that were
> missing before have been restored.  thanks!
>
> I just noticed that i cannot get directly to the datastore entries viewer
> - i have to search for the datastore item, click into it, wait for it to
> load, and then select entries and wait for it to load.  this was 1 click in
> the old console.  There are many actions that were 1 click and took much
> less time to load that are now buried under multiple clicks with slow load
> times of the intermediate pages.
>
> It looks like the pagination links are missing from the task queue task
> viewer.  I was just trying to diagnose something with my tasks and can't
> look at any tasks beyond the first 100 in the queue. :(
>
> Thanks for all the attention to helping make this a great tool for us!
>
> Christian
>
>
>
> On Saturday, March 5, 2016 at 3:40:10 PM UTC-8, Lorne Kligerman wrote:
>>
>> I appreciate the detailed description here, it helps a lot in reproducing
>> on our side.
>> I'm curious to hear about individual deep links that seem to be missing.
>> Christian, could you or others elaborate?
>>
>>
>> On Wednesday, March 2, 2016 at 4:59:03 PM UTC-8, Nickolas Daskalou wrote:
>>>
>>> For me, the new Cloud Console is more aesthetically pleasing, and it is
>>> indeed nice to have all of Google Cloud in one aggregated console.
>>>
>>> It can, however, get very clunky at times.
>>>
>>> The new Logs viewer is a perfect example of this. E.g. hitting enter in
>>> the search box works most of the time, but then there are occasions where
>>> nothing happens. Type in an extra search query, or delete an existing
>>> search item, hit Enter, then nothing. No change in the log items list.
>>> Auto refresh on scroll up/down can be good, until it doesn't work. Then it
>>> gets super frustrating. Clicking on the refresh and play buttons, work
>>> well, until they don't. I've also seen the date/time input clobbered,
>>> seemingly randomly.
>>>
>>> If I'm on the new Logs viewer page for more than a few minutes at a
>>> time, I find myself having to constantly reload the page to get it working
>>> again. A simple refresh will not do, because the browser's current address
>>> bar URL changes as you use the Logs viewer, and it's possible a simple
>>> refresh will result in a similar unresponsive, quirky view you were already
>>> on.
>>>
>>> So instead, when I want to refresh the Logs viewer (which occurs 90% of
>>> the time I have been on the page for more than a few minutes), I need to
>>> manually delete most of the current URL to get back to the base, "starting"
>>> Logs viewer URL for my current project.
>>>
>>> I sometimes think about Celine Dion's Titanic song, you know the one
>>> that goes "every night in my dreams, I see you, I feel you"? I feel that
>>> way about the " *· · ·* Loading..." mini status popup in the new Logs
>>> viewer. It haunts me, and sometimes it just won't go away.
>>>
>>> The new Cloud Console feels half-baked. Well, 80% baked. At least the
>>> App Engine parts do. Or rather, the App Engine parts I use. Another
>>> example: "Could not load instances information. [Dismiss link]" in the App
>>> Engine -> Versions page constantly pops up when I'm trying to switch
>>> between modules. Constantly.
>>>
>>> Also, this guy:
>>>
>>> [image: Inline images 2]
>>>
>>> Sometimes he just can't take the hint and leave.
>>>
>>> However, as the Iron Sheik once said, besides that everything was great.
>>>
>>> Nick
>>>
>>>
>>> On 3 March 2016 at 11:33, Christian F. Howes <
>>> christi...@starmakerinteractive.com> wrote:
>>>
 Lorne,

 the other things that hinder us in a measurable way are page load
 times, lack of direct links to individual pages, and finding where things
 are (including having some things missing from the search index).

 on a personal opinion level I really miss having all my app engine
 management tools 1 click away with a full listing in the sidebar.  now
 several of them are 2 clicks away.

 thanks for the continued improvements!  things are getting better in
 the new console and it's close to ready for the switch.

 christian


 On 3/2/16 16:02, 'Lorne Kligerman' via Google App Engine wrote:

> We are working to improve our attention to the public issue tracker,
> something we acknowledge has slipped but it is by no means an

Re: [google-appengine] New Cloud Console

[Christian F. Howes]

Lorne,

First off the link to customer support is buried inside some menu option 
that does not show up in search.
While never officially supported, the customer support team taught me how 
to link to an individual log record in the old console.  This has really 
helped me both with internal QA and with customer support tickets.
The links to individual datastore records and query results that were 
missing before have been restored.  thanks!

I just noticed that i cannot get directly to the datastore entries viewer - 
i have to search for the datastore item, click into it, wait for it to 
load, and then select entries and wait for it to load.  this was 1 click in 
the old console.  There are many actions that were 1 click and took much 
less time to load that are now buried under multiple clicks with slow load 
times of the intermediate pages.

It looks like the pagination links are missing from the task queue task 
viewer.  I was just trying to diagnose something with my tasks and can't 
look at any tasks beyond the first 100 in the queue. :(

Thanks for all the attention to helping make this a great tool for us!

Christian



On Saturday, March 5, 2016 at 3:40:10 PM UTC-8, Lorne Kligerman wrote:
>
> I appreciate the detailed description here, it helps a lot in reproducing 
> on our side.  
> I'm curious to hear about individual deep links that seem to be missing. 
>  Christian, could you or others elaborate?
>
>
> On Wednesday, March 2, 2016 at 4:59:03 PM UTC-8, Nickolas Daskalou wrote:
>>
>> For me, the new Cloud Console is more aesthetically pleasing, and it is 
>> indeed nice to have all of Google Cloud in one aggregated console.
>>
>> It can, however, get very clunky at times.
>>
>> The new Logs viewer is a perfect example of this. E.g. hitting enter in 
>> the search box works most of the time, but then there are occasions where 
>> nothing happens. Type in an extra search query, or delete an existing 
>> search item, hit Enter, then nothing. No change in the log items list. 
>> Auto refresh on scroll up/down can be good, until it doesn't work. Then it 
>> gets super frustrating. Clicking on the refresh and play buttons, work 
>> well, until they don't. I've also seen the date/time input clobbered, 
>> seemingly randomly.
>>
>> If I'm on the new Logs viewer page for more than a few minutes at a time, 
>> I find myself having to constantly reload the page to get it working again. 
>> A simple refresh will not do, because the browser's current address bar URL 
>> changes as you use the Logs viewer, and it's possible a simple refresh will 
>> result in a similar unresponsive, quirky view you were already on.
>>
>> So instead, when I want to refresh the Logs viewer (which occurs 90% of 
>> the time I have been on the page for more than a few minutes), I need to 
>> manually delete most of the current URL to get back to the base, "starting" 
>> Logs viewer URL for my current project.
>>
>> I sometimes think about Celine Dion's Titanic song, you know the one that 
>> goes "every night in my dreams, I see you, I feel you"? I feel that way 
>> about the " *· · ·* Loading..." mini status popup in the new Logs 
>> viewer. It haunts me, and sometimes it just won't go away.
>>
>> The new Cloud Console feels half-baked. Well, 80% baked. At least the App 
>> Engine parts do. Or rather, the App Engine parts I use. Another example: 
>> "Could not load instances information. [Dismiss link]" in the App Engine -> 
>> Versions page constantly pops up when I'm trying to switch between modules. 
>> Constantly.
>>
>> Also, this guy:
>>
>> [image: Inline images 2]
>>
>> Sometimes he just can't take the hint and leave.
>>
>> However, as the Iron Sheik once said, besides that everything was great.
>>
>> Nick
>>
>>
>> On 3 March 2016 at 11:33, Christian F. Howes <
>> christi...@starmakerinteractive.com> wrote:
>>
>>> Lorne,
>>>
>>> the other things that hinder us in a measurable way are page load times, 
>>> lack of direct links to individual pages, and finding where things are 
>>> (including having some things missing from the search index).
>>>
>>> on a personal opinion level I really miss having all my app engine 
>>> management tools 1 click away with a full listing in the sidebar.  now 
>>> several of them are 2 clicks away.
>>>
>>> thanks for the continued improvements!  things are getting better in the 
>>> new console and it's close to ready for the switch.
>>>
>>> christian
>>>
>>>
>>> On 3/2/16 16:02, 'Lorne Kligerman' via Google App Engine wrote:
>>>
 We are working to improve our attention to the public issue tracker,
 something we acknowledge has slipped but it is by no means an indication
 that these items are not important to us and our engineering teams.

 Besides the items already mentioned here (usage history, migrate 
 traffic,
 logs), could you elaborate on what else would limit your ability to 
 manage
 your app from the Cloud Console?

 On Thursday, 

Re: [google-appengine] New Cloud Console

[Christian F. Howes]

Hi Nick,

Can you just review cloud support case 08706899 for which PIT issues are 
not properly updated?  I've listed them out there in the original filing of 
the case and the response from the support team is that several of them are 
fixed.

Thanks,

Christian

On Monday, March 7, 2016 at 11:15:49 AM UTC-8, Nick (Cloud Platform 
Support) wrote:
>
> Hey Chris,
>
> If you could link which issues those are which have been fixed but not 
> updated, we could take a look and determine whether they should be updated 
> with any new relevant information, such as a fix. Feel free to reply to me 
> in this thread.
>
> Best wishes,
>
> Nick
>
> On Thursday, February 25, 2016 at 1:09:43 PM UTC-5, Christian F. Howes 
> wrote:
>>
>> Thanks Lorne. 
>>
>> Will we also be better at triaging and updating the Public Issue 
>> Tracker?  Paid support told me today that several of the issues I filed 
>> last year are supposedly fixed, but the Public Issue Tracker has yet to 
>> be updated. 
>>
>> The lack of information provided, but the hard deadline on the turn-down 
>> notice really concerns me as I don't have confidence that I will be able 
>> to efficiently and effectively manage my app 6 weeks from now. 
>>
>> Thanks, 
>>
>> Christian 
>>
>> On 2/25/16 04:49, 'Lorne Kligerman' via Google App Engine wrote: 
>> > Thanks everyone for the feedback.  Overall, we are going to reach 
>> feature 
>> > parity in the Cloud Platform Console before turning down the Admin 
>> Console. 
>> >   The next communication we send will have more details and will 
>> outline any 
>> > gaps that exist and our plans to address them.  To answer the questions 
>> > asked here: 
>> > 
>> > - the dispatch rules will not be visible right away, but we are 
>> actively 
>> > working on a mechanism for you to view all of your App Engine 
>> configuration 
>> > in one place 
>> > - prohibiting code downloads will not show up in the same way, but this 
>> can 
>> > be managed through roles and upcoming IAM functionality 
>> > - as mentioned already, performance is a known issue that is a top 
>> priority 
>> > for the team 
>> > 
>> > Please continue to log issues as Nick mentioned and we will triage 
>> > accordingly. 
>> > 
>> > Cheers, 
>> > Lorne. 
>> > 
>> > On Thursday, February 25, 2016 at 6:13:25 AM UTC-5, troberti wrote: 
>> >> 
>> >> 1+ for speed. Also, is the requests/seconds coming to the new console? 
>> At 
>> >> least for me that's an easier value to discuss. Besides, the new 
>> console's 
>> >> request/minute do not match the request/second metric in the old 
>> console. 
>> >> 
>> >> On Thursday, February 25, 2016 at 11:20:34 AM UTC+1, Mark Cummins 
>> wrote: 
>> >>> 
>> >>> +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 

Re: [google-appengine] New Cloud Console

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Nickolas,

If you can, capture the tab's activity during the error into a HAR file 
, you should post that 
to the Public Issue Tracker 
, attaching the 
"Restrict-View-EditIssue" label, so that only Google and yourself can view 
it. We'll be in touch shortly after the thread is created.

Best wishes,

Nick
Cloud Platform Community Support

On Monday, March 7, 2016 at 6:27:49 PM UTC-5, Nickolas Daskalou wrote:
>
> Hi Lorne / Nick,
>
> Yet another new issue with the Logs viewer which just occurred about 5 
> minutes ago.
>
> Upon visiting the Logs viewer for 2 different projects, this error popped 
> up before any logs were shown, then disappeared after about 5 seconds 
> without me doing anything (and finally logs were indeed shown):
>
> [image: Inline images 1]
>
> Nick
>
>
>
> On 8 March 2016 at 06:15, 'Nick (Cloud Platform Support)' via Google App 
> Engine  wrote:
>
>> Hey Chris,
>>
>> If you could link which issues those are which have been fixed but not 
>> updated, we could take a look and determine whether they should be updated 
>> with any new relevant information, such as a fix. Feel free to reply to me 
>> in this thread.
>>
>> Best wishes,
>>
>> Nick
>>
>>
>> On Thursday, February 25, 2016 at 1:09:43 PM UTC-5, Christian F. Howes 
>> wrote:
>>>
>>> Thanks Lorne. 
>>>
>>> Will we also be better at triaging and updating the Public Issue 
>>> Tracker?  Paid support told me today that several of the issues I filed 
>>> last year are supposedly fixed, but the Public Issue Tracker has yet to 
>>> be updated. 
>>>
>>> The lack of information provided, but the hard deadline on the turn-down 
>>> notice really concerns me as I don't have confidence that I will be able 
>>> to efficiently and effectively manage my app 6 weeks from now. 
>>>
>>> Thanks, 
>>>
>>> Christian 
>>>
>>> On 2/25/16 04:49, 'Lorne Kligerman' via Google App Engine wrote: 
>>> > Thanks everyone for the feedback.  Overall, we are going to reach 
>>> feature 
>>> > parity in the Cloud Platform Console before turning down the Admin 
>>> Console. 
>>> >   The next communication we send will have more details and will 
>>> outline any 
>>> > gaps that exist and our plans to address them.  To answer the 
>>> questions 
>>> > asked here: 
>>> > 
>>> > - the dispatch rules will not be visible right away, but we are 
>>> actively 
>>> > working on a mechanism for you to view all of your App Engine 
>>> configuration 
>>> > in one place 
>>> > - prohibiting code downloads will not show up in the same way, but 
>>> this can 
>>> > be managed through roles and upcoming IAM functionality 
>>> > - as mentioned already, performance is a known issue that is a top 
>>> priority 
>>> > for the team 
>>> > 
>>> > Please continue to log issues as Nick mentioned and we will triage 
>>> > accordingly. 
>>> > 
>>> > Cheers, 
>>> > Lorne. 
>>> > 
>>> > On Thursday, February 25, 2016 at 6:13:25 AM UTC-5, troberti wrote: 
>>> >> 
>>> >> 1+ for speed. Also, is the requests/seconds coming to the new 
>>> console? At 
>>> >> least for me that's an easier value to discuss. Besides, the new 
>>> console's 
>>> >> request/minute do not match the request/second metric in the old 
>>> console. 
>>> >> 
>>> >> On Thursday, February 25, 2016 at 11:20:34 AM UTC+1, Mark Cummins 
>>> wrote: 
>>> >>> 
>>> >>> +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 
>>> >> 
>>> >> 
>>> 

Re: [google-appengine] New Cloud Console

[Nickolas Daskalou]

Hi Lorne / Nick,

Yet another new issue with the Logs viewer which just occurred about 5
minutes ago.

Upon visiting the Logs viewer for 2 different projects, this error popped
up before any logs were shown, then disappeared after about 5 seconds
without me doing anything (and finally logs were indeed shown):

[image: Inline images 1]

Nick



On 8 March 2016 at 06:15, 'Nick (Cloud Platform Support)' via Google App
Engine  wrote:

> Hey Chris,
>
> If you could link which issues those are which have been fixed but not
> updated, we could take a look and determine whether they should be updated
> with any new relevant information, such as a fix. Feel free to reply to me
> in this thread.
>
> Best wishes,
>
> Nick
>
>
> On Thursday, February 25, 2016 at 1:09:43 PM UTC-5, Christian F. Howes
> wrote:
>>
>> Thanks Lorne.
>>
>> Will we also be better at triaging and updating the Public Issue
>> Tracker?  Paid support told me today that several of the issues I filed
>> last year are supposedly fixed, but the Public Issue Tracker has yet to
>> be updated.
>>
>> The lack of information provided, but the hard deadline on the turn-down
>> notice really concerns me as I don't have confidence that I will be able
>> to efficiently and effectively manage my app 6 weeks from now.
>>
>> Thanks,
>>
>> Christian
>>
>> On 2/25/16 04:49, 'Lorne Kligerman' via Google App Engine wrote:
>> > Thanks everyone for the feedback.  Overall, we are going to reach
>> feature
>> > parity in the Cloud Platform Console before turning down the Admin
>> Console.
>> >   The next communication we send will have more details and will
>> outline any
>> > gaps that exist and our plans to address them.  To answer the questions
>> > asked here:
>> >
>> > - the dispatch rules will not be visible right away, but we are
>> actively
>> > working on a mechanism for you to view all of your App Engine
>> configuration
>> > in one place
>> > - prohibiting code downloads will not show up in the same way, but this
>> can
>> > be managed through roles and upcoming IAM functionality
>> > - as mentioned already, performance is a known issue that is a top
>> priority
>> > for the team
>> >
>> > Please continue to log issues as Nick mentioned and we will triage
>> > accordingly.
>> >
>> > Cheers,
>> > Lorne.
>> >
>> > On Thursday, February 25, 2016 at 6:13:25 AM UTC-5, troberti wrote:
>> >>
>> >> 1+ for speed. Also, is the requests/seconds coming to the new console?
>> At
>> >> least for me that's an easier value to discuss. Besides, the new
>> console's
>> >> request/minute do not match the request/second metric in the old
>> console.
>> >>
>> >> On Thursday, February 25, 2016 at 11:20:34 AM UTC+1, Mark Cummins
>> wrote:
>> >>>
>> >>> +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 

Re: [google-appengine] New Cloud Console

['Nick (Cloud Platform Support)' via Google App Engine]

Hey Chris,

If you could link which issues those are which have been fixed but not 
updated, we could take a look and determine whether they should be updated 
with any new relevant information, such as a fix. Feel free to reply to me 
in this thread.

Best wishes,

Nick

On Thursday, February 25, 2016 at 1:09:43 PM UTC-5, Christian F. Howes 
wrote:
>
> Thanks Lorne. 
>
> Will we also be better at triaging and updating the Public Issue 
> Tracker?  Paid support told me today that several of the issues I filed 
> last year are supposedly fixed, but the Public Issue Tracker has yet to 
> be updated. 
>
> The lack of information provided, but the hard deadline on the turn-down 
> notice really concerns me as I don't have confidence that I will be able 
> to efficiently and effectively manage my app 6 weeks from now. 
>
> Thanks, 
>
> Christian 
>
> On 2/25/16 04:49, 'Lorne Kligerman' via Google App Engine wrote: 
> > Thanks everyone for the feedback.  Overall, we are going to reach 
> feature 
> > parity in the Cloud Platform Console before turning down the Admin 
> Console. 
> >   The next communication we send will have more details and will outline 
> any 
> > gaps that exist and our plans to address them.  To answer the questions 
> > asked here: 
> > 
> > - the dispatch rules will not be visible right away, but we are actively 
> > working on a mechanism for you to view all of your App Engine 
> configuration 
> > in one place 
> > - prohibiting code downloads will not show up in the same way, but this 
> can 
> > be managed through roles and upcoming IAM functionality 
> > - as mentioned already, performance is a known issue that is a top 
> priority 
> > for the team 
> > 
> > Please continue to log issues as Nick mentioned and we will triage 
> > accordingly. 
> > 
> > Cheers, 
> > Lorne. 
> > 
> > On Thursday, February 25, 2016 at 6:13:25 AM UTC-5, troberti wrote: 
> >> 
> >> 1+ for speed. Also, is the requests/seconds coming to the new console? 
> At 
> >> least for me that's an easier value to discuss. Besides, the new 
> console's 
> >> request/minute do not match the request/second metric in the old 
> console. 
> >> 
> >> On Thursday, February 25, 2016 at 11:20:34 AM UTC+1, Mark Cummins 
> wrote: 
> >>> 
> >>> +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
>  
> >> <
> https://groups.google.com/d/msgid/google-appengine/540d27f2-1841-4be8-a21b-17aea883dd84%40googlegroups.com?utm_medium=email_source=footer>
>  
>
> >> . 
> >> For more options, visit https://groups.google.com/d/optout. 
> >> 
> >> 

Re: [google-appengine] New Cloud Console

['Lorne Kligerman' via Google App Engine]

I appreciate the detailed description here, it helps a lot in reproducing 
on our side.  
I'm curious to hear about individual deep links that seem to be missing. 
 Christian, could you or others elaborate?


On Wednesday, March 2, 2016 at 4:59:03 PM UTC-8, Nickolas Daskalou wrote:
>
> For me, the new Cloud Console is more aesthetically pleasing, and it is 
> indeed nice to have all of Google Cloud in one aggregated console.
>
> It can, however, get very clunky at times.
>
> The new Logs viewer is a perfect example of this. E.g. hitting enter in 
> the search box works most of the time, but then there are occasions where 
> nothing happens. Type in an extra search query, or delete an existing 
> search item, hit Enter, then nothing. No change in the log items list. 
> Auto refresh on scroll up/down can be good, until it doesn't work. Then it 
> gets super frustrating. Clicking on the refresh and play buttons, work 
> well, until they don't. I've also seen the date/time input clobbered, 
> seemingly randomly.
>
> If I'm on the new Logs viewer page for more than a few minutes at a time, 
> I find myself having to constantly reload the page to get it working again. 
> A simple refresh will not do, because the browser's current address bar URL 
> changes as you use the Logs viewer, and it's possible a simple refresh will 
> result in a similar unresponsive, quirky view you were already on.
>
> So instead, when I want to refresh the Logs viewer (which occurs 90% of 
> the time I have been on the page for more than a few minutes), I need to 
> manually delete most of the current URL to get back to the base, "starting" 
> Logs viewer URL for my current project.
>
> I sometimes think about Celine Dion's Titanic song, you know the one that 
> goes "every night in my dreams, I see you, I feel you"? I feel that way 
> about the " *· · ·* Loading..." mini status popup in the new Logs viewer. 
> It haunts me, and sometimes it just won't go away.
>
> The new Cloud Console feels half-baked. Well, 80% baked. At least the App 
> Engine parts do. Or rather, the App Engine parts I use. Another example: 
> "Could not load instances information. [Dismiss link]" in the App Engine -> 
> Versions page constantly pops up when I'm trying to switch between modules. 
> Constantly.
>
> Also, this guy:
>
> [image: Inline images 2]
>
> Sometimes he just can't take the hint and leave.
>
> However, as the Iron Sheik once said, besides that everything was great.
>
> Nick
>
>
> On 3 March 2016 at 11:33, Christian F. Howes <
> christi...@starmakerinteractive.com > wrote:
>
>> Lorne,
>>
>> the other things that hinder us in a measurable way are page load times, 
>> lack of direct links to individual pages, and finding where things are 
>> (including having some things missing from the search index).
>>
>> on a personal opinion level I really miss having all my app engine 
>> management tools 1 click away with a full listing in the sidebar.  now 
>> several of them are 2 clicks away.
>>
>> thanks for the continued improvements!  things are getting better in the 
>> new console and it's close to ready for the switch.
>>
>> christian
>>
>>
>> On 3/2/16 16:02, 'Lorne Kligerman' via Google App Engine wrote:
>>
>>> We are working to improve our attention to the public issue tracker,
>>> something we acknowledge has slipped but it is by no means an indication
>>> that these items are not important to us and our engineering teams.
>>>
>>> Besides the items already mentioned here (usage history, migrate traffic,
>>> logs), could you elaborate on what else would limit your ability to 
>>> manage
>>> your app from the Cloud Console?
>>>
>>> On Thursday, February 25, 2016 at 10:09:43 AM UTC-8, Christian F. Howes
>>> wrote:
>>>

 Thanks Lorne.

 Will we also be better at triaging and updating the Public Issue
 Tracker?  Paid support told me today that several of the issues I filed
 last year are supposedly fixed, but the Public Issue Tracker has yet to
 be updated.

 The lack of information provided, but the hard deadline on the turn-down
 notice really concerns me as I don't have confidence that I will be able
 to efficiently and effectively manage my app 6 weeks from now.

 Thanks,

 Christian

 On 2/25/16 04:49, 'Lorne Kligerman' via Google App Engine wrote:

> Thanks everyone for the feedback.  Overall, we are going to reach
>
 feature

> parity in the Cloud Platform Console before turning down the Admin
>
 Console.

>The next communication we send will have more details and will 
> outline
>
 any

> gaps that exist and our plans to address them.  To answer the questions
> asked here:
>
> - the dispatch rules will not be visible right away, but we are 
> actively
> working on a mechanism for you to view all of your App Engine
>
 configuration

> in one place
> - prohibiting 

Re: [google-appengine] New Cloud Console

[Nickolas Daskalou]

For me, the new Cloud Console is more aesthetically pleasing, and it is
indeed nice to have all of Google Cloud in one aggregated console.

It can, however, get very clunky at times.

The new Logs viewer is a perfect example of this. E.g. hitting enter in the
search box works most of the time, but then there are occasions where
nothing happens. Type in an extra search query, or delete an existing
search item, hit Enter, then nothing. No change in the log items list.
Auto refresh on scroll up/down can be good, until it doesn't work. Then it
gets super frustrating. Clicking on the refresh and play buttons, work
well, until they don't. I've also seen the date/time input clobbered,
seemingly randomly.

If I'm on the new Logs viewer page for more than a few minutes at a time, I
find myself having to constantly reload the page to get it working again. A
simple refresh will not do, because the browser's current address bar URL
changes as you use the Logs viewer, and it's possible a simple refresh will
result in a similar unresponsive, quirky view you were already on.

So instead, when I want to refresh the Logs viewer (which occurs 90% of the
time I have been on the page for more than a few minutes), I need to
manually delete most of the current URL to get back to the base, "starting"
Logs viewer URL for my current project.

I sometimes think about Celine Dion's Titanic song, you know the one that
goes "every night in my dreams, I see you, I feel you"? I feel that way
about the " *· · ·* Loading..." mini status popup in the new Logs viewer.
It haunts me, and sometimes it just won't go away.

The new Cloud Console feels half-baked. Well, 80% baked. At least the App
Engine parts do. Or rather, the App Engine parts I use. Another example:
"Could not load instances information. [Dismiss link]" in the App Engine ->
Versions page constantly pops up when I'm trying to switch between modules.
Constantly.

Also, this guy:

[image: Inline images 2]

Sometimes he just can't take the hint and leave.

However, as the Iron Sheik once said, besides that everything was great.

Nick


On 3 March 2016 at 11:33, Christian F. Howes <
christian.ho...@starmakerinteractive.com> wrote:

> Lorne,
>
> the other things that hinder us in a measurable way are page load times,
> lack of direct links to individual pages, and finding where things are
> (including having some things missing from the search index).
>
> on a personal opinion level I really miss having all my app engine
> management tools 1 click away with a full listing in the sidebar.  now
> several of them are 2 clicks away.
>
> thanks for the continued improvements!  things are getting better in the
> new console and it's close to ready for the switch.
>
> christian
>
>
> On 3/2/16 16:02, 'Lorne Kligerman' via Google App Engine wrote:
>
>> We are working to improve our attention to the public issue tracker,
>> something we acknowledge has slipped but it is by no means an indication
>> that these items are not important to us and our engineering teams.
>>
>> Besides the items already mentioned here (usage history, migrate traffic,
>> logs), could you elaborate on what else would limit your ability to manage
>> your app from the Cloud Console?
>>
>> On Thursday, February 25, 2016 at 10:09:43 AM UTC-8, Christian F. Howes
>> wrote:
>>
>>>
>>> Thanks Lorne.
>>>
>>> Will we also be better at triaging and updating the Public Issue
>>> Tracker?  Paid support told me today that several of the issues I filed
>>> last year are supposedly fixed, but the Public Issue Tracker has yet to
>>> be updated.
>>>
>>> The lack of information provided, but the hard deadline on the turn-down
>>> notice really concerns me as I don't have confidence that I will be able
>>> to efficiently and effectively manage my app 6 weeks from now.
>>>
>>> Thanks,
>>>
>>> Christian
>>>
>>> On 2/25/16 04:49, 'Lorne Kligerman' via Google App Engine wrote:
>>>
 Thanks everyone for the feedback.  Overall, we are going to reach

>>> feature
>>>
 parity in the Cloud Platform Console before turning down the Admin

>>> Console.
>>>
The next communication we send will have more details and will
 outline

>>> any
>>>
 gaps that exist and our plans to address them.  To answer the questions
 asked here:

 - the dispatch rules will not be visible right away, but we are actively
 working on a mechanism for you to view all of your App Engine

>>> configuration
>>>
 in one place
 - prohibiting code downloads will not show up in the same way, but this

>>> can
>>>
 be managed through roles and upcoming IAM functionality
 - as mentioned already, performance is a known issue that is a top

>>> priority
>>>
 for the team

 Please continue to log issues as Nick mentioned and we will triage
 accordingly.

 Cheers,
 Lorne.

 On Thursday, February 25, 2016 at 6:13:25 AM UTC-5, troberti wrote:

>
> 1+ for 

Re: [google-appengine] New Cloud Console

[Christian F. Howes]

Lorne,

the other things that hinder us in a measurable way are page load times, 
lack of direct links to individual pages, and finding where things are 
(including having some things missing from the search index).


on a personal opinion level I really miss having all my app engine 
management tools 1 click away with a full listing in the sidebar.  now 
several of them are 2 clicks away.


thanks for the continued improvements!  things are getting better in the 
new console and it's close to ready for the switch.


christian

On 3/2/16 16:02, 'Lorne Kligerman' via Google App Engine wrote:

We are working to improve our attention to the public issue tracker,
something we acknowledge has slipped but it is by no means an indication
that these items are not important to us and our engineering teams.

Besides the items already mentioned here (usage history, migrate traffic,
logs), could you elaborate on what else would limit your ability to manage
your app from the Cloud Console?

On Thursday, February 25, 2016 at 10:09:43 AM UTC-8, Christian F. Howes
wrote:


Thanks Lorne.

Will we also be better at triaging and updating the Public Issue
Tracker?  Paid support told me today that several of the issues I filed
last year are supposedly fixed, but the Public Issue Tracker has yet to
be updated.

The lack of information provided, but the hard deadline on the turn-down
notice really concerns me as I don't have confidence that I will be able
to efficiently and effectively manage my app 6 weeks from now.

Thanks,

Christian

On 2/25/16 04:49, 'Lorne Kligerman' via Google App Engine wrote:

Thanks everyone for the feedback.  Overall, we are going to reach

feature

parity in the Cloud Platform Console before turning down the Admin

Console.

   The next communication we send will have more details and will outline

any

gaps that exist and our plans to address them.  To answer the questions
asked here:

- the dispatch rules will not be visible right away, but we are actively
working on a mechanism for you to view all of your App Engine

configuration

in one place
- prohibiting code downloads will not show up in the same way, but this

can

be managed through roles and upcoming IAM functionality
- as mentioned already, performance is a known issue that is a top

priority

for the team

Please continue to log issues as Nick mentioned and we will triage
accordingly.

Cheers,
Lorne.

On Thursday, February 25, 2016 at 6:13:25 AM UTC-5, troberti wrote:


1+ for speed. Also, is the requests/seconds coming to the new console?

At

least for me that's an easier value to discuss. Besides, the new

console's

request/minute do not match the request/second metric in the old

console.


On Thursday, February 25, 2016 at 11:20:34 AM UTC+1, Mark Cummins

wrote:


+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

<

https://groups.google.com/d/msgid/google-appengine/540d27f2-1841-4be8-a21b-17aea883dd84%40googlegroups.com?utm_medium=email_source=footer>


.
For more options, visit https://groups.google.com/d/optout.











--
You 

Re: [google-appengine] New Cloud Console

['Lorne Kligerman' via Google App Engine]

We are working to improve our attention to the public issue tracker, 
something we acknowledge has slipped but it is by no means an indication 
that these items are not important to us and our engineering teams.

Besides the items already mentioned here (usage history, migrate traffic, 
logs), could you elaborate on what else would limit your ability to manage 
your app from the Cloud Console?

On Thursday, February 25, 2016 at 10:09:43 AM UTC-8, Christian F. Howes 
wrote:
>
> Thanks Lorne. 
>
> Will we also be better at triaging and updating the Public Issue 
> Tracker?  Paid support told me today that several of the issues I filed 
> last year are supposedly fixed, but the Public Issue Tracker has yet to 
> be updated. 
>
> The lack of information provided, but the hard deadline on the turn-down 
> notice really concerns me as I don't have confidence that I will be able 
> to efficiently and effectively manage my app 6 weeks from now. 
>
> Thanks, 
>
> Christian 
>
> On 2/25/16 04:49, 'Lorne Kligerman' via Google App Engine wrote: 
> > Thanks everyone for the feedback.  Overall, we are going to reach 
> feature 
> > parity in the Cloud Platform Console before turning down the Admin 
> Console. 
> >   The next communication we send will have more details and will outline 
> any 
> > gaps that exist and our plans to address them.  To answer the questions 
> > asked here: 
> > 
> > - the dispatch rules will not be visible right away, but we are actively 
> > working on a mechanism for you to view all of your App Engine 
> configuration 
> > in one place 
> > - prohibiting code downloads will not show up in the same way, but this 
> can 
> > be managed through roles and upcoming IAM functionality 
> > - as mentioned already, performance is a known issue that is a top 
> priority 
> > for the team 
> > 
> > Please continue to log issues as Nick mentioned and we will triage 
> > accordingly. 
> > 
> > Cheers, 
> > Lorne. 
> > 
> > On Thursday, February 25, 2016 at 6:13:25 AM UTC-5, troberti wrote: 
> >> 
> >> 1+ for speed. Also, is the requests/seconds coming to the new console? 
> At 
> >> least for me that's an easier value to discuss. Besides, the new 
> console's 
> >> request/minute do not match the request/second metric in the old 
> console. 
> >> 
> >> On Thursday, February 25, 2016 at 11:20:34 AM UTC+1, Mark Cummins 
> wrote: 
> >>> 
> >>> +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
>  
> >> <
> 

Re: [google-appengine] New Cloud Console

[Christian F. Howes]

Thanks Lorne.

Will we also be better at triaging and updating the Public Issue 
Tracker?  Paid support told me today that several of the issues I filed 
last year are supposedly fixed, but the Public Issue Tracker has yet to 
be updated.


The lack of information provided, but the hard deadline on the turn-down 
notice really concerns me as I don't have confidence that I will be able 
to efficiently and effectively manage my app 6 weeks from now.


Thanks,

Christian

On 2/25/16 04:49, 'Lorne Kligerman' via Google App Engine wrote:

Thanks everyone for the feedback.  Overall, we are going to reach feature
parity in the Cloud Platform Console before turning down the Admin Console.
  The next communication we send will have more details and will outline any
gaps that exist and our plans to address them.  To answer the questions
asked here:

- the dispatch rules will not be visible right away, but we are actively
working on a mechanism for you to view all of your App Engine configuration
in one place
- prohibiting code downloads will not show up in the same way, but this can
be managed through roles and upcoming IAM functionality
- as mentioned already, performance is a known issue that is a top priority
for the team

Please continue to log issues as Nick mentioned and we will triage
accordingly.

Cheers,
Lorne.

On Thursday, February 25, 2016 at 6:13:25 AM UTC-5, troberti wrote:


1+ for speed. Also, is the requests/seconds coming to the new console? At
least for me that's an easier value to discuss. Besides, the new console's
request/minute do not match the request/second metric in the old console.

On Thursday, February 25, 2016 at 11:20:34 AM UTC+1, Mark Cummins wrote:


+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/56CF4349.4020801%40starmakerinteractive.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] New Cloud Console

['Lorne Kligerman' via Google App Engine]

Thanks everyone for the feedback.  Overall, we are going to reach feature 
parity in the Cloud Platform Console before turning down the Admin Console. 
 The next communication we send will have more details and will outline any 
gaps that exist and our plans to address them.  To answer the questions 
asked here:

- the dispatch rules will not be visible right away, but we are actively 
working on a mechanism for you to view all of your App Engine configuration 
in one place
- prohibiting code downloads will not show up in the same way, but this can 
be managed through roles and upcoming IAM functionality
- as mentioned already, performance is a known issue that is a top priority 
for the team

Please continue to log issues as Nick mentioned and we will triage 
accordingly.

Cheers,
Lorne.

On Thursday, February 25, 2016 at 6:13:25 AM UTC-5, troberti wrote:
>
> 1+ for speed. Also, is the requests/seconds coming to the new console? At 
> least for me that's an easier value to discuss. Besides, the new console's 
> request/minute do not match the request/second metric in the old console.
>
> On Thursday, February 25, 2016 at 11:20:34 AM UTC+1, Mark Cummins wrote:
>>
>> +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/34981984-025e-4068-b9de-2a5ac99149c7%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.

Re: [google-appengine] New Cloud Console

[Christian F. Howes]

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/1e7c959f-224b-458c-96c0-c1ff498034ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] New Cloud Console

[Rajkumar Radhakrishnan]

Hi,

Google App Engine has been offering an option to "permanently prohibit code
downloads." ever since launch in April 2008. This action was available for
users with "Admin" and "Developer" role and is currently available in the
Versions page of old Admin Console, like shown in the image below.

[image: Inline image 1]


The new Cloud Platform Console does not seem to offer this option. Before
the old Admin Console is to be phased out completely, this facility needs
to be available in some form in the new Cloud Platform Console.

This "permanently prohibit code downloads" option was useful to help enable
developers deploy software to multiple customers, each having their own
datastore, billing settings, backup configuration, etc.,. while also
assuring the developer that the code will remain safe from being downloaded
off from Google servers.

Since a "Marketplace for Google App Engine apps" as detailed in
https://code.google.com/p/googleappengine/issues/detail?id=5821

.. is not yet available, this is the only option available to license
software run-times, without providing access to the binaries and the source
code.

I have also raised an issue, so that developers can star and be notified of
the change in issue status:
https://code.google.com/p/googleappengine/issues/detail?id=12763

Thanks & regards,
Raj

On Wed, Feb 24, 2016 at 11:31 AM, Stefano Ciccarelli <
stefano.ciccare...@mmbsoftware.it> wrote:

> And what about the dispatch? If you have a dispatch configured you can
> view it only on the old console!
>
> Il giorno mer 24 feb 2016 alle 01:44 'Lorne Kligerman' via Google App
> Engine  ha scritto:
>
>> 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/6aa5997d-6d50-406a-bae4-7eb972035283%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> *Stefano Ciccarelli*
> GAE Application Division
> / Director
> stefano.ciccare...@mmbsoftware.it
>
> *M.M.B. s.r.l.*
> via Granarolo, 177/7 - 48018 Faenza (RA) - Italy
> tel. +39.0546.637711 - fax +39.0546.46077
> www.mmbsoftware.it - i...@mmbsoftware.it
>
> Le informazioni contenute in questa comunicazione sono riservate e
> destinate esclusivamente alla/e persona/e o all'ente sopra indicati. E'
> vietato ai soggetti diversi dai destinatari qualsiasi uso, copia,
> diffusione di quanto in esso contenuto sia ai sensi dell'art. 616 c.p., sia
> ai sensi del DL n. 196/03. Se questa comunicazione Vi e' pervenuta per
> errore, Vi preghiamo di rispondere a questa e-mail e successivamente
> cancellarla dal Vostro sistema.
>
> --
> 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 

Re: [google-appengine] New Cloud Console

[Stefano Ciccarelli]

And what about the dispatch? If you have a dispatch configured you can view
it only on the old console!

Il giorno mer 24 feb 2016 alle 01:44 'Lorne Kligerman' via Google App
Engine  ha scritto:

> 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/6aa5997d-6d50-406a-bae4-7eb972035283%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
*Stefano Ciccarelli*
GAE Application Division
/ Director
stefano.ciccare...@mmbsoftware.it

*M.M.B. s.r.l.*
via Granarolo, 177/7 - 48018 Faenza (RA) - Italy
tel. +39.0546.637711 - fax +39.0546.46077
www.mmbsoftware.it - i...@mmbsoftware.it

Le informazioni contenute in questa comunicazione sono riservate e
destinate esclusivamente alla/e persona/e o all'ente sopra indicati. E'
vietato ai soggetti diversi dai destinatari qualsiasi uso, copia,
diffusione di quanto in esso contenuto sia ai sensi dell'art. 616 c.p., sia
ai sensi del DL n. 196/03. Se questa comunicazione Vi e' pervenuta per
errore, Vi preghiamo di rispondere a questa e-mail e successivamente
cancellarla dal Vostro sistema.

-- 
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/CAArRkeW7jMciyKbKX5bcvjV3qZ2%2B4%2BJxZMkFj4YzfKcWy48M9A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] New Cloud Console

[johnP]

Good news - thanks.



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/15820ccf-09e3-49d4-a8fe-eace05f8ffe1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] New Cloud Console

['Lorne Kligerman' via Google App Engine]

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/6aa5997d-6d50-406a-bae4-7eb972035283%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] New Cloud Console

[PK]

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-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/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/628C2C5A-A0E3-42D4-BB4D-08482CA1F3F1%40gae123.com.
For more options, visit https://groups.google.com/d/optout.