App engine stdout logs missing from Logs Explorer

39 views
Skip to first unread message

Patrick Rodjito

unread,
Nov 30, 2020, 11:30:53 AM11/30/20
to Google App Engine

The load generator is writing a large amount of test logs (~5000 every second) to stdout for testing purposes. Each log entry is about 2KB. We noticed that only about a third of the logs show up in Logs Explorer. This seems to be a function of log size, that is if the size of each test log entry is reduced, then a greater proportion of the logs show up as expected in Logs Explorer.

Here are a few examples. All of these logs are generated at a rate of 5000 per second:

About 0.3 KB per log entry. Almost all the expected logs show up in  Logs Explorer. Slight losses.

About 3.4 KB per log entry. About 40,000 out of 50,000 showed up in Logs Explorer.

About 12 KB per log entry. About 20,000 out of 50,000 showed up in Logs Explorer.

Looking at the GAE logging documentation, there's no mention of sampling of any kind so I'm stumped as to why this is happening. To be clear, this is happening before logging sinks so this is definitely not caused by exclusion rules.

Thank you!


Lucas Bart Torre

unread,
Nov 30, 2020, 6:31:35 PM11/30/20
to Google App Engine
Hello,

Google Groups isn't meant for troubleshooting.

This seems to be a bug in App Engine, which we can't really do much with here.

Please file a bug over at https://bit.ly/appengine-bug

Regards

Patrick Rodjito

unread,
Dec 1, 2020, 1:52:02 AM12/1/20
to google-a...@googlegroups.com
Thank you! I have filed the bug here.

--
You received this message because you are subscribed to a topic in the Google Groups "Google App Engine" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-appengine/ndtjEFzBaeo/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-appengi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/7f4a70f6-b9fa-48dd-bea1-b1e1228d71c0n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages