devnw / alog Goto Github PK

So users can create a destination that has an internal testing.T or testing.B object which the io.Writer logs to for errors / logs rather than stdout/stderr so that test outputs show appropriately.

This seems to be something people look for in loggers so it should be supported in a way that fits into the simplified API for alog

This should allow for a user to deregister a log level or destination at runtime.

This should accept a channel of interface which then reads in values and properly routes them throughout the logger based on interfaces that are implemented on the inputs.

This should be able to add new destinations and level registrations in a manner that doesn't interfere with the existing registrations and allows new registrations to begin receiving new logs immediately.

This would contain the parent logger internally but would have the ability to add supplementary information in the child logs.

Could follow a similar pattern to context in how it nests.

The Wait() method should properly block until the alog instance has properly closed all internal channels and written all remaining logs to the registered IO.

When a context is closed the current implementation will exit out of all logging without draining the channel first. This can cause logs to be lost because they are not pulled prior to exiting.

Each channel should be monitored using something like len of the channel to ensure that all logs are drained prior to exiting the logger. Obviously, this doesn't solve the case where the application is closed, but perhaps an option should be added to monitor for an os signal and drain remaining logs when that happens.

https://github.com/benjivesterby/alog/blob/ecc21a0324c77b6085daeb25187d8a6a8a8bf2e4/alog.go#L97

Define an interface which looks similar to this

type streamers interface {
    Events() <-chan interface{}
}

That can be registered into the alog system. There should be the ability to have 0-N of these registered and alog should pull events from them and log them to the appropriate destinations based on their interface types.

Internal interface types for it to recognize would be initially error and stringer which would go to the Error and Print methods of alog respectively. This should be extensible in the future to be able to add additional error types. This registration system should be able to use the same c method types which accept interface types.