Since this morning, something has changed in the “Logs Explorer” of our App Engine project, and the log lines no longer display the logMessage when opened, right after the request. Now, to view the messages, it is necessary to open the log and expand the protopayload > line fields to see the different lines of the messages within the JSON. It’s a bit complicated to explain; I hope it is understood.
Yesterday night, it was working well and displaying all the information.
Has there been any change in the UI or in the way logs are displayed? Is this happening only to us, or is it a widespread issue?
I noticed the same symptom on the same day (Jan-24-Wed). It’s still not fixed. I saw it in logs from App Engine Standard Environment Python 2.7, how about you? I also noticed that the problem exists not only for recent logs, but also for old logs that didn’t have the problem last time I looked at them, so the problem is apparently in the viewer, not the logs themselves.
Yes, the same here. Python 2.7 GAE standard. Old logs too.
It seems that in Python 3 it is normal that correlated logs do not work as they did before in Python 2, but in our case we have not yet migrated to Python 3 and it will take a few days/weeks.
I don’t know if our case has to do with the end of support for Python 2.7, but it doesn’t look like they intend to solve it.
Mostly yes. Since Sunday Feb-04 the line.logMessage data is showing as nested rows again for non-split requests. For requests that get split into multiple parent rows related by an operation.id, only the last parent row shows its line.logMessage data as nested rows.
(I am also still working on migrating out of App Engine Python 2.7. In our case we’re moving to Cloud Run and sticking with Python 2.7 a while longer, because updating our code to deal with big incompatible changes in much newer libraries that support Python 3.9 will be even harder.)