Command line log needs a rethink

[sapiderman]

It seems to me the cli output is too noisy, too much information.

example snapshot:

2021-04-18T04:46:36.992Z,PROBE,2,0,https://github.com,200,1475
2021-04-18T04:46:36.993Z,ALERT,response-time-greater-than-500-ms,2,2,0,https://github.com,200,1475
2021-04-18T04:46:41.042Z,PROBE,3,1,http://worldtimeapi.org/api/ip,200,513
2021-04-18T04:46:41.044Z,ALERT,response-time-greater-than-500-ms,1,3,1,http://worldtimeapi.org/api/ip,200,513
2021-04-18T04:46:42.014Z,PROBE,3,0,https://github.com,200,1493
2021-04-18T04:46:42.015Z,ALERT,response-time-greater-than-500-ms,3,3,0,https://github.com,200,1493
2021-04-18T04:46:42.016Z,NOTIFY-INCIDENT,response-time-greater-than-500-ms,smtp,mail trap id,0,https://github.com

It's hard to digest and see whats happenign at a glance. There's too much information. Some information are multiline and redundant

Perhaps we can clean it up a bit. For instance:

2021-04-18T04:52:44.817Z, id:1, 200 http://worldtimeapi.org/api/ip, 320ms
2021-04-18T04:52:45.711Z, id:0, 200 https://github.com, 1609ms ALERT!
2021-04-18T04:52:50.067Z, id:1, 500 http://worldtimeapi.org/api/ip, 947ms ALERT!
2021-04-18T04:52:50.982Z, id:0, 401 https://github.com/auth, 1893ms ALERT! Service is probaby down

Everything you need to know is on a single line. Alerts highlight the trigger (response code or resposne time) and a flag "ALERT!"

[ time ], [ id ], [ status ], [ url ], [ response time ], [ALERT flag if any] [ INFO additional status if any ]

When there's nothing to report merely output
2021-04-18T04:52:44.817Z, id:1, 200 http://somedomain.com/api/, 320ms
2021-04-18T04:52:45.711Z, id:0, 200 https://github.com, 109ms

Here's what it may look like with alerts.

[sapiderman]

what do you guys think of this?

[sapiderman]

or with hostname?