Thanks to everyone for clarifying their use case. When initially testing the differences between the two, I arrived at these similar results (see attached screenshots).
I do not believe however, that these exemplify the kinda of threading you are describing. As such, please submit a Feature Request <https://code.google.com/p/googleappengine/issues/entry?template=Feature%20request> with as much information as possible including the helpful description above and screenshots of examples. I would then strongly encourage that you post a link to the issue here and each 'star' the issue along with other relevant issues posted above to give as much attention as possible to issues important to the community. On Thursday, February 25, 2016 at 4:41:25 AM UTC-5, ThePiachu wrote: > > In the old logs, I was able to neatly see all logs by thread - every > warning, error and debug was in chronological order, sorted by the thread > that initialized them. Now it seems everything is jumbled together, clumped > a few entries at a time and shuffled between multiple simultaneous threads. > > Is there any way for me to read the new logs in a threaded fashion, > especially int he light of the old console going away? > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/30fd80fc-6511-4a58-ae80-63caf21ff18f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
