Benchmark Data

Summary Links

svcrunner/jsonlog.

svcrunner/jsonlog

Benchmark Data

Score: 98.04

Benchmark	Runs	Ns/Op	Allocs/Op	Bytes/Op	MB/Sec	Score
Attributes	1,000,000	1,091.00	3	280	382.23	98.92
Big Group	12,662	96,323.00	17	139,398	270.70	85.64
Disabled	407,603,260	2.94	0	0	0.00	100.00
Key Values	1,000,000	1,138.00	3	280	366.33	98.94
Logging	57,078	21,071.00	0	0	427.13	99.31
Simple	4,220,899	277.30	0	0	313.68	98.53
Simple Source	4,461,201	276.60	0	0	314.58	99.64
With Attrs Attributes	1,000,000	1,123.00	4	288	693.95	99.10
With Attrs Key Values	1,000,000	1,147.00	4	288	678.07	99.14
With Attrs Simple	3,508,118	356.80	1	8	1,258.31	99.25
With Group Attributes	1,000,000	1,109.00	4	296	387.89	99.12
With Group Key Values	968,470	1,205.00	4	296	357.74	98.92

Benchmark Charts

Warnings

Score: 72.31

Required

LevelVar Unable to change level during execution via LevelVar

Slog handlers can use LevelVar to specify the handler logging level. Unlike specifying a Level (which is actually an int), a LevelVar is supposed to be changeable during program execution.

Verify: Level Var		level not changed

SlogTest Failure of embedded slog/slogtest

Documentation on building a handler suggests testing using slog/slogtest, part of the Go release since 1.21. While the verification suite includes tests patterned after those in slogtest, an additional single test invokes the slogtest testing sequence (involving multiple tests). Since this is a separate package, all error messages are returned at once. This is the only warning that affects TestSlogTest and all of its error messages.

Verify: Slog Test

missing key "msg"
this test expects slog.TimeKey, slog.LevelKey and slog.MessageKey

missing key "msg"
a Handler should handle the WithGroup method

missing key "msg"
a Handler should handle multiple WithGroup and WithAttr calls

missing key "msg"
a Handler should not output groups if there are no attributes

Implied

MessageKey Wrong message key (should be 'msg')

The field name of the "message" key should be msg.

Verify: Canceled Context		`message`

Verify: Canceled Context		`message`

Verify: Canceled Context		`message`

Verify: Keys		`message`

Verify: Source Key		`message`

Verify: Zero PC		`message`

Verify: Zero Time		`message`

NoEmptyName Attributes with empty names are not logged

Until documented otherwise, an attribute with an empty field name ("") should be logged.

Empty field names are logged by the JSONHandler.Handle() implementation

Verify: Attribute Empty Name
	{ "first": "one", "level": "INFO", "message": "This is a message", "pi": 3.141592653589793, "time": "2024-05-19T01:15:07.479663937Z" }
Verify: Attribute With Empty Name
	{ "first": "one", "level": "INFO", "message": "This is a message", "pi": 3.141592653589793, "time": "2024-05-19T01:15:07.479913222Z" }
Verify: Attributes Not Empty
	{ "first": "one", "level": "INFO", "message": "This is a message", "pi": 3.141592653589793, "time": "2024-05-19T01:15:07.480149112Z" }
Verify: Attributes With Not Empty
	{ "first": "one", "level": "INFO", "message": "This is a message", "pi": 3.141592653589793, "second": 2, "time": "2024-05-19T01:15:07.480323938Z" }

NoReplAttr HandlerOptions.ReplaceAttr not available

If HandlerOptions.ReplaceAttr is provided it should be honored by the handler. However, documentation on implementing handler methods seems to suggest it is optional.

Verify: Replace Attr		too many attributes: 6, alpha == beta, change still exists, remove still exists

Verify: Replace Attr Basic		time field still exists message field still exists source ==

Verify: Replace Attr Fn Change Key		too few attributes: 3 no message key message not string

Verify: Replace Attr Fn Level Case		level value not null

Verify: Replace Attr Fn Multi
	{ "group": { "alpha": "omega", "pi": 3.141592653589793, "subGroup": { "alpha": "omega", "e": 2.718281828459045, "goober": "snoofus", "oneMore": { "alpha": "omega", "gibbering": "lunatic", "phi": 1.618033988749895 } } }, "level": "INFO", "message": "This is a message", "time": "2024-05-19T01:15:07.482503242Z" }
Verify: Replace Attr Fn Remove Empty Key

Verify: Replace Attr Fn Remove Time		time value not empty string

SourceKey Source data not logged when AddSource flag set

Handlers should log source data when the slog.HandlerOptions.AddSource flag is set.

Bench: Simple Source		no 'source' key
	{ "level": "INFO", "message": "This is a message", "time": "2024-05-19T01:14:58.867907855Z" }
Verify: Source Key		no 'source' key
	{ "level": "INFO", "message": "This is a message", "time": "2024-05-19T01:15:07.483088423Z" }

Suggested

Duplicates Duplicate field(s) found

Some handlers (e.g. slog.JSONHandler) will output multiple occurrences of the same field name if the logger is called with multiple instances of the same field, generally by using WithAttrs and then the same fields in the eventual log call (e.g. Info). This behavior is currently under debate with no resolution at this time (2024-01-15) and a release milestone of (currently unscheduled) Go 1.23, (whereas Go Release 1.22 is currently expected in February 2024).

Verify: Attribute Duplicate		map[alpha:2 charlie:3]

Verify: Attribute With Duplicate		map[alpha:2 charlie:3]

DurationString slog.Duration() logs a string representation instead of nanoseconds

The slog.JSONHandler uses nanoseconds for time.Duration but some other handlers use a string representation.

Verify: Group Duration		8h3m22s
	{ "group": { "inner": "8h3m22s" }, "level": "INFO", "message": "This is a message", "outer": "8h3m22s", "time": "2024-05-19T01:15:07.481577936Z" }
Verify: Log Attributes		1m0s
	{ "any": [ "alpha", "omega" ], "boolean": true, "goober": "snoofus", "howLong": "1m0s", "level": "INFO", "message": "This is a message", "minus": -64, "pi": 3.141592653589793, "skidoo": 23, "time": "2024-05-19T01:15:07.482203673Z", "unsigned": 79, "when": "2024-05-19T01:15:07.482202351Z" }

Handler svcrunner/jsonlog

Benchmark Data

Benchmark Charts

Warnings