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, 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 <jo...@thinkwave.com> 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&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-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/56D7865F.7060809%40starmakerinteractive.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/962535d0-a6f1-40b1-8db8-e4e604f7ee76%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
