**see shy jo** @joeyh@octodon.social · May 22, 2018, 15:17

**see shy jo** @joeyh@octodon.social · May 22, 2018, 15:17

see shy jo @joeyh@octodon.social

@liw do you have any advice for machine-parsable error messages?

(across programming language boundaries)

**Lars Wirzenius** @liw · 2018-05-22T17:16:24Z

Lars Wirzenius @liw

@joeyh I'm currently doing json encoded as one physical line per message. See git.liw.fi/slog

May 22, 2018, 17:16 · Tusky · 1 · 0

**see shy jo** @joeyh@octodon.social · May 22, 2018, 17:20

**see shy jo** @joeyh@octodon.social · May 22, 2018, 17:20

@liw do you have some kind of unique id for an error?

**Lars Wirzenius** @liw · May 22, 2018, 17:28

**Lars Wirzenius** @liw · May 22, 2018, 17:28

@joeyh not in slog. i did have that for obnam. see the obnam repository, http://git.liw.fi/obnam/tree/obnamlib/structurederror.py

**Daniel Barlow 🚴** @telent@mastodon.social · May 22, 2018, 18:02

**Daniel Barlow 🚴** @telent@mastodon.social · May 22, 2018, 18:02

@liw @joeyh i like one entry/line and first field as iso8601 timestamp, then I can use Unix tools for simpme stuff when I don't want to break out the json parser