4

Stackdriver logs seems to truncate log lines exceeding ~256 chars. This is really annoying, since Stackdriver also doesn't let you filter for log lines matching a particular string, and then find its neighboring log lines.

Our use case is that sometimes, we want to log a very long message (e.g., a stack trace). Then, we want to be able to filter for those messages via an identifier that only appears in the first line. We can't output the message across multiple lines, since we when we filter, we can only find the first line and not neighboring lines. We also can't output the entire message onto 1 line, since Stackdriver truncates us at ~256 chars. This makes debugging many errors nearly impossible.

FTR, oddly, I'm not always truncated at exactly 256 chars - sometimes it's 260, sometimes 256, and I assume other times it can be in between.

Alternately, is there another way to view Google Cloud ML logs than Stackdriver?

jwayne
  • 706
  • 2
  • 7
  • 20
  • 1
    The Stackdriver Logging limit on log entry sizes is 100KB (https://cloud.google.com/logging/quota-policy), so I'm guessing that CloudML is truncating it. I'll see what I can track down. – Kirk Kelsey Mar 10 '17 at 20:59
  • 1
    I'm a product manager with Stackdriver Logging. There was also an issue where the UI was truncating lines. This should now be resolved (or shortly resolved as the fix is rolled out). – Mary Koes Mar 21 '17 at 15:20

1 Answers1

1

Your log may be visible as dropdown attribute, e.g. jsonPayload

imgur screenshot

johnmcs
  • 429
  • 4
  • 10
  • Thanks. I think this feature is new as of the rollouts mentioned in the comments posted under my question. – jwayne Mar 22 '17 at 15:09