NOTE: I'm not a 'go' programmer by trade and I love the diagrams python module you created...thanks for your contributions!

While using your tool to generate some logs while performance testing a log shipper setup, I noticed the timestamp in the emitted logs (while using the -l forever option), slowly became further and further behind the current time. This made it appear that the log shipper was lagging behind.

A basic test I performed was as follows:

Run the flog generator

./flog -f json -o /tmp/json.log -t log -d 1ms -l

In another terminal, every few seconds compare the last log line with the current date:

tail -1 /tmp/json.log && date

What you'll notice is the timestamp in the last log line slowly gets behind from the current time.

I was able to make a minor modification to flog.go which corrected the problem:

diff --git a/flog.go b/flog.go
index 896026b..728a1dc 100644
--- a/flog.go
    b/flog.go
@@ -38,7  38,7 @@ func Generate(option *Option) error {
        if option.Forever {
                for {
                        time.Sleep(delay)
-                       log := NewLog(option.Format, created)
                        log := NewLog(option.Format, time.Now())
                        _, _ = writer.Write([]byte(log   "\n"))
                        created = created.Add(interval)
                }

EDIT: Your implementation allows for better precision (using delays less than 1ms), it's just the slow skew that I'm not sure can be completely accounted for since the load generator requires some wall time to execute as well.