structured logging: support log messages with line breaks

[pohly]

What this PR does / why we need it:

The initial structured logging output (almost) always produced a single line
per log message, with quoting of strings to represent line breaks as \n. This
made the output hard to read (see
kubernetes/kubernetes#104868).

It was still possible to get line breaks when formatting a value with %+v and
that ended up emitting line breaks; this was probably not intended.

Now the message is never quoted, as in non-structured output. String values are
quoted if they contain no line break. If they do, start/end markers delimit the
text which appears on its own lines.

All additional lines of a structure log message get indented by one space. This
makes it obvious where a new log message starts, which is an improvement
compared to the traditional format.

Which issue(s) this PR fixes:

Fixes kubernetes/kubernetes#106262, kubernetes/kubernetes#106428

Special notes for your reviewer:

Traditional output:

I1112 14:06:35.783354  328441 structured_logging.go:42] someData printed using InfoF: {hello world 0}
I1112 14:06:35.783472  328441 structured_logging.go:43] longData printed using InfoF: {long Multiple
lines
with quite a bit
of text. 0}
I1112 14:06:35.783483  328441 structured_logging.go:44] stringData printed using InfoF,
with the message across multiple lines:
long: Multiple
lines
with quite a bit
of text.
I1112 14:06:35.898176  142908 structured_logging.go:54] logData printed using InfoF:
{log output from some program I0000 12:00:00.000000  123456 main.go:42] Starting
E0000 12:00:01.000000  123456 main.go:43] Failed for some reason
 0}

Old InfoS output before this commit:

I1112 14:06:35.783512  328441 structured_logging.go:50] "using InfoS" someData={Name:hello Data:world internal:0}
I1112 14:06:35.783529  328441 structured_logging.go:51] "using InfoS" longData={Name:long Data:Multiple
lines
with quite a bit
of text. internal:0}
I1112 14:06:35.783549  328441 structured_logging.go:52] "using InfoS with\nthe message across multiple lines" nt=1 stringData="long: Multiple\nlines\nwith quite a bit\nof text." str="another value"
I1112 14:06:35.898278  142908 structured_logging.go:65] "using InfoS" logData={Name:log output from some program Data:I0000 12:00:00.000000  123456 main.go:42] Starting
E0000 12:00:01.000000  123456 main.go:43] Failed for some reason
 internal:0}
I1112 14:06:35.783565  328441 structured_logging.go:61] "Did something" item="foobar"
I1112 14:06:35.783576  328441 structured_logging.go:63] "This is a full sentence." item="foobar"

New InfoS output:

I1119 13:18:00.210970   78836 structured_logging.go:58] using InfoS | someData={Name:hello Data:world internal:0}
I1119 13:18:00.210988   78836 structured_logging.go:59] using InfoS | longData>>>
 {Name:long Data:Multiple
 lines
 with quite a bit
 of text. internal:0}
 <<<
I1119 13:18:00.211009   78836 structured_logging.go:60] using InfoS with
 the message across multiple lines | int=1 stringData>>>
 long: Multiple
 lines
 with quite a bit
 of text.
 <<< str="another value"
I1119 13:18:00.211032   78836 structured_logging.go:65] using InfoS | logData>>>
 {Name:log output from some program Data:I0000 12:00:00.000000  123456 main.go:42] Starting
 E0000 12:00:01.000000  123456 main.go:43] Failed for some reason
  internal:0}
 <<<
I1119 13:18:00.211068   78836 structured_logging.go:71] Did something | item="foobar"
I1119 13:18:00.211079   78836 structured_logging.go:73] This is a full sentence. item="foobar"

Release note:

In structured output (= InfoS, ErrorS), values with line breaks will be printed across multiple lines to make the output more readable. The message is also not quoted anymore and may stretch across multiple lines. Every new line gets indented by one space.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: pohly
To complete the pull request process, please assign justinsb after the PR has been reviewed.
You can assign the PR to them by writing /assign @justinsb in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[pohly]

I'm open for suggestions regarding the markup for string start and end...

[pohly]

Another alternative is with the key name repeated inside the start/end tags instead of the normal printing as variable name:

 <previous key/value> vvvvv multiLine vvvvv
 ....
 ^^^^^ multiLine ^^^^^
 <next key/value>

"multiLine" here is the key for the key/value pair, not some special hard-coded delimiter as "string" is in the current PR.

[pohly]

The message string for InfoS has the same problem. I also find the quotation marks around the text distracting. On the other hand, we may want to provide some hint on where the message text ends and key/value pairs start.

[pohly]

I ended up revamping the entire formatting. See updated description and the new example for a comparison.

[pohly]

This is ready for review of the concept. I might still do some performance improvements.

/cc @shivanshu1333 @serathius
/wg structured-logging
/sig instrumentation
/priority important-soon
/milestone 1.23
/area logging
/kind feature

[k8s-ci-robot]

@pohly: The label(s) area/logging cannot be applied, because the repository doesn't have them.

In response to this:

This is ready for review of the concept. I might still do some performance improvements.

/cc @shivanshu1333 @serathius
/wg structured-logging
/sig instrumentation
/priority important-soon
/milestone 1.23
/area logging
/kind feature

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[serathius]

I don't see any benefit of adding built in markers for logs. They

• don't make logs more readable as users can klog header to already distinguish start vs end of multi line log
• adding standard markers makes parsing logs harder, existing kubernetes log parsers already should handle multi line log.
• Increases log volume

K8s logs already have multi line logs that provide their own markers, thus I think we should leave it up user to provide
them themselves.

[pohly]

I think there's a misunderstanding. The markers are not delimiters for messages. They are delimiters for values.

With the current InfoS format, the quotation marks provides those delimiters. But they result in output that is basically unreadable for a human, which defeats the purpose of the text output.

[pohly]

Increases log volume

That's a valid point. We could make them shorter. For example:

I1112 15:01:48.696677  413871 structured_logging.go:52] using InfoS with
 the message across multiple lines: int=1 stringData>>>
 long: Multiple
 lines
 with quite a bit
 of text.
 <<< str="another value"

That's four bytes (>>> plus newline) instead of two (=") and three bytes (<<<) instead of one (") at the end.

Line breaks are the same with new line plus space instead of \n.

If the text contains many quotation marks, this format might actually be shorter because those don't need to be escaped.

[serathius]

Does strings.Split here needlessly copies the string into slices?

[pohly]

Yes. I'll add benchmarking and make the code more efficient before merging. Right now I am only looking for feedback on the format.

/hold

[pohly]

#273 has detailed benchmark data.

[serathius]

I don't agree with this change, we decided on quoting the string as this gives us predictable and somewhat parsable output (not everyone will imminently switch to JSON). Idea of quoting was related to message being treated as structured metadata. This is based on idea that JSON uses "msg" key to store message, so we though that message should be written as other string values with one difference of msg= being skipped.

[pohly]

I don't agree with this change,

This PR or the line you commented on, the : separator? I can drop that separator, it's not important.

But quoting is a major problem. I get what was meant to be achieved with it, but IMHO the effect on readability was not considered. it now prevents conversion to structured logging because developers will complain or even go as far as filing bugs and reverting the conversion.

[shivanshuraj1333]

I agree with Marek, JSON should not become a dependency for log parsing, the raw log output should be parsable

[pohly]

The current text format is not machine-readable. If that was the goal, then we have bugs in its implementation around handling of structs.

[pohly]

So as you are both against this proposal, how do you suggest we should deal with cases where developers want multi-line output in a readable format (kubernetes/kubernetes#104868)?

[serathius]

I think we should separate how we consider multi line for different part of logs. In my opinion multiline:

• doesn't make sense for log messages. They should be a short description of what event is happening in system. Their format should not differ much or at all between different log formats. For example as I user that switched between log formats I want to be able to find log I have seen in old format in the new format just by grepping the message.
• doesn't make sense for log keys. They should strive to uniquely identify types of metadata attached to log. Strive comes from idea that over time a schema will develop that will have a predictable way to find values under specific keys. Their names should follow a strict convention to avoid diverging.
• can make sense for complex values when debugging. I assumed handling this case is needed Scheduler logged config prints without line breaks kubernetes#104868. There are multiple cases in k8s logs that multiline logs are used to improve readability. We should allow users to customize that some values (for example dumping whole k8s object yaml) are written in multiline format.

[pohly]

can make sense for complex values when debugging.

Agreed.

We should allow users to customize that some values (for example dumping whole k8s object yaml) are written in multiline format.

And how to you propose to do that?

We need an API for it and a serialization format that log parsers then will understand.

[pohly]

In my opinion multiline doesn't make sense for log messages.

I can buy that argument. So let me propose a solution just for multi-line values in #273

I'm going to close this PR here in favor of that one.

/close

[shivanshuraj1333]

Can we think about using some other separator here? I've seen many logs use something like klog.InfoS("Warning: some text", key, value)

[pohly]

Perhaps |, with a space before and after it?

[pohly]

When comparing this change with kubernetes/kubernetes#106594 (comment) shows that the new format is slightly smaller: 61450443 bytes vs. 60583121 bytes for a kubelet log with 268551 messages and 310746 key/value pairs in those messages.

[k8s-ci-robot]

@pohly: Closed this PR.

In response to this:

In my opinion multiline doesn't make sense for log messages.

I can buy that argument. So let me propose a solution just for multi-line values in #273

I'm going to close this PR here in favor of that one.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.