Hacker News Reader

Comment by owebmaster | Hacker News Reader

An OutOfMemoryException log should not be the same as a search log

  Error: OutOfMemoryException

And

  Search: OutOfMemoryException

Should not be related in any way

View on HN

Until someone searches for "Error: OutOfMemoryException"

If structured logging is too much, unique prefixes solve this issue. Basically you need some token that user provided data is unable to output to the log. If you rigorously escape all newlines, you can then use start-of-line and end-of-line as unforgeable tokens. The possibilities are endless and it all comes down to understanding whether the intersection of two grammars is empty.

I read the gp to mean that error.log (being parsed to look for OOM) would have no associations with userSearches.log, in which an end-user searched for OOM

Reply on news.ycombinator.com