The log formats supported

Creates a logger given a log format Also takes an useNetstrings argument which is there because we cannot immediatelly deprecate the old interface. Old configs only provide the useNetstrings argument and not the logFormat argument, and in that case implement the old behaviour of either enabling plain text logging or netstring logging. If both arguments are set, logFormat takes presedence over useNetstrings

FUTUREWORK: Once we get rid of the useNetstrings in our config files, we can remove this function and rename mkLoggerNew to mkLogger

Like mkLogger, but uses Log.new which reads in LOG_* env variables.

TODO: DEPRECATED! Use mkLogger instead and get all settings from config files, not from environment!

It's a bit odd that we mention MonadClient from the cql-io package here, but it's the easiest way to get things done. Alternatively, we could introduce LoggerT in the gundeck integration tests, which is the only place in the world where it is currently used, but we may need it elsewhere in the future and here it's easier to find.

Here for backwards-compatibility reasons

Displays all the Bytes segments in a list under key msgs and Field segments as key-value pair in a JSON

>>> logElems = [Bytes "W", Bytes "The message", Field "field1" "val1", Field "field2" "val2", Field "field1" "val1.1"]
>>> B.toLazyByteString $ structuredJSONRenderer "," iso8601UTC Info logElems
"{\"msgs\":[\"The message\"],\"field1\":[\"val1\",\"val1.1\"],\"field2\":\"val2\",\"level\":\"Warn\"}"