Geert-Johan Riemer

@ChrisHines I just updated the PR. I rewrote the complete code, there's no external dependency anymore. There's no buffering anymore, the logs are being sent to Loggly immediately. Please let...

Ah well, there **is** one external dependency: `github.com/pquerna/ffjson/fflib/v1`. But I trust the maintainers of that project to not make any breaking changes. They even versioned this dependency and breaking changes...

@inconshreveable You're right, I'm updating the code right now.

There, removed the `const` and `var`'s and have `Endpoint` as exported field.

Loggly strongly recommends sending JSON for this type of thing. They do indeed accept all kind of logs so that you can pipe apache, nginx, syslog, etc. etc. directly to...

I've pushed a work in progress test, but it's not working.. Looks like a problem with the channel (might be a Go issue on tip). To be continued later.

It really makes no sense to send anything other than JSON to Loggly, unless you don't have JSON. For the File, Stream and Net handlers this does make sense, because...

If someone does really require to set a custom Formatter for some reason, then they can either fork the LogglyHandler and add it with a few lines of code. And...

@ChrisHines Good point, I can definitely see that as a use-case, especially in larger cluster systems that should be able to handle connectivity downtime without losing information. @inconshreveable I would...

@ChrisHines Excelent point! I hope you don't mind I've opened a new issue for it. @inconshreveable What do you think about `ext` ?