datalust / seq-forwarder

Local collection and reliable forwarding of log data to Seq
Apache License 2.0
57 stars 15 forks source link

Official Docker image #54

Open coderpatros opened 3 years ago

coderpatros commented 3 years ago

Hi team!

Any current plans to create a docker image for this? Just don't want to go to the trouble of creating one if you are already working on it.

nblumhardt commented 3 years ago

Hi Patrick! Definitely on the radar but we probably won't get this implemented/automated for a little while; I have a few more TODOs in mind that I'd like to do first, like environment variable-based config... I'd better raise a few issues :-)

Will leave this open to track - thanks! 👍

coderpatros commented 3 years ago

Thanks @nblumhardt

feitzi commented 3 years ago

Is the docker image already on your backlog? We definitely want to use that in our K8 Cluster to archive interruption-free Seq Updates and Pod movements, but we are not sure if it's the correct way with seq-forwarder because it seems is not in active development.

nblumhardt commented 3 years ago

Thanks for sending a note @feitzi; it's definitely our intention to maintain Seq Forwarder and develop it further.

I've been hoping for some feedback on v2 before we move forward with it, but, I think it's probably time we just ploughed ahead :-)

It should quite straightforward to put together the Docker image now that the prerequisites are all sorted.

I'll merge #53 and let's take it from there :-)

dazinator commented 1 year ago

Just chiming in to say, would really like a docker image for this. Would it be possible to send the forwarder docker logs (e.g https://docs.datalust.co/docs/collecting-docker-container-logs) and have those forwarded? I am considering a scenario where the seq server is on different infrastructure to the docker swarm, so being able to buffer the logs at the forwarder will help provide better resiliency should the seq server go down for a period, or there be some type of transient network fault between the environments.

nblumhardt commented 1 year ago

Thanks for the nudge @dazinator. Still keen to do this but as yet unscheduled.

The Docker log collection instructions you linked use GELF as the transport, which seq-forwarder doesn't support, so you may need a different solution there (Fluent Bit supports a wide range of input protocols, can buffer to disk, and can easily forward to Seq using an output config like the one in https://blog.datalust.co/tailing-a-log-file-or-folder-with-fluent-bit-and-seq/).

HTH!