Transactor emits too much log data with INFO level which makes it difficult to separate important realtime metrics/events from low level stuff useful only for troubleshooting. E.g.:
`
2024-12-23 12:14:42.147 INFO default datomic.kv-cluster - {:event :kv-cluster/create-val, :val-key "67695432-37bb-4155-9731-0ad26be7e1de", :bufsize 882, :msec 5.65, :phase :end, :pid 9, :tid 692}
2024-12-23 12:14:42.151 INFO default datomic.kv-cluster - {:event :kv-cluster/create-val, :val-key "67695432-11c9-4b95-85dc-1d081032a132", :bufsize 1170, :msec 6.64, :phase :end, :pid 9, :tid 694}
...
2024-12-23 12:32:35.033 INFO default datomic.log-gc - {:gcName "G1 Young Generation", :gcAction "end of minor GC", :gcCause "GCLocker Initiated GC", :event :gc, :duration 70, :pid 9, :tid 5}
2024-12-23 12:32:35.396 INFO default datomic.log-gc - {:gcName "G1 Young Generation", :gcAction "end of minor GC", :gcCause "G1 Evacuation Pause", :event :gc, :duration 63, :pid 9, :tid 5}
2024-12-23 12:32:35.749 INFO default datomic.log-gc - {:gcName "G1 Young Generation", :gcAction "end of minor GC", :gcCause "GCLocker Initiated GC", :event :gc, :duration 49, :pid 9, :tid 5}
2024-12-23 12:32:36.135 INFO default datomic.log-gc - {:gcName "G1 Young Generation", :gcAction "end of minor GC", :gcCause "G1 Evacuation Pause", :event :gc, :duration 68, :pid 9, :tid 5}
2024-12-23 12:32:36.487 INFO default datomic.log-gc - {:gcName "G1 Young Generation", :gcAction "end of minor GC", :gcCause "GCLocker Initiated GC", :event :gc, :duration 65, :pid 9, :tid 5}
2024-12-23 12:32:36.853 INFO default datomic.log-gc - {:gcName "G1 Young Generation", :gcAction "end of minor GC", :gcCause "GCLocker Initiated GC", :event :gc, :duration 55, :pid 9, :tid 5}
2024-12-23 12:32:37.239 INFO default datomic.log-gc - {:gcName "G1 Young Generation", :gcAction "end of minor GC", :gcCause "G1 Evacuation Pause", :event :gc, :duration 73, :pid 9, :tid 5}
2024-12-23 12:32:37.615 INFO default datomic.log-gc - {:gcName "G1 Young Generation", :gcAction "end of minor GC", :gcCause "G1 Evacuation Pause", :event :gc, :duration 65, :pid 9, :tid 5}
2024-12-23 12:32:37.961 INFO default datomic.log-gc - {:gcName "G1 Young Generation", :gcAction "end of minor GC", :gcCause "G1 Evacuation Pause", :event :gc, :duration 69, :pid 9, :tid 5}
2024-12-23 12:32:38.285 INFO default datomic.log-gc - {:gcName "G1 Young Generation", :gcAction "end of minor GC", :gcCause "G1 Evacuation Pause", :event :gc, :duration 58, :pid 9, :tid 5}
2024-12-23 12:32:38.713 INFO default datomic.log-gc - {:gcName "G1 Young Generation", :gcAction "end of minor GC", :gcCause "G1 Evacuation Pause", :event :gc, :duration 68, :pid 9, :tid 5}
2024-12-23 12:32:39.039 INFO default datomic.log-gc - {:gcName "G1 Young Generation", :gcAction "end of minor GC", :gcCause "G1 Evacuation Pause", :event :gc, :duration 62, :pid 9, :tid 5}
2024-12-23 12:32:39.364 INFO default datomic.log-gc - {:gcName "G1 Young Generation", :gcAction "end of minor GC", :gcCause "G1 Evacuation Pause", :event :gc, :duration 66, :pid 9, :tid 5}
2024-12-23 12:32:39.721 INFO default datomic.log-gc - {:gcName "G1 Young Generation", :gcAction "end of minor GC", :gcCause "G1 Evacuation Pause", :event :gc, :duration 78, :pid 9, :tid 5}
2024-12-23 12:32:39.923 INFO default datomic.lifecycle - {:tid 19, :username "krVN7t+5clwdg5/HazGJsrE0ckBlt50uk+HlYn9vbwY=", :port 4334, :rev 4243344, :host "0.0.0.0", :pid 9, :event :transactor/heartbeat, :version "1.0.7187", :timestamp 1734957159894, :encrypt-channel true}
`
It would be nice to review log levels and have a paper on messages generated with INFO level. Also the log line seems to be EDN for which there is no parser on ELK/Grafana side. Can this be made JSON to enable structural logging?
