Add TLS Support about seq-input-gelf HOT 6 CLOSED

Anything happened here related to TLS? Currently we are looking into the topic of getting GELF formatted messages (from php) to Seq.

from seq-input-gelf.

Thanks for the ping, @luscit. No, unfortunately, we haven't made any progress on this recently. We're keen to push this forward, but won't be able to schedule work here before the 2021.3 release makes it out the door (currently late October).

(If anyone following along is interested in sketching up a proposal or sending a PR before then, it would be most welcome.)

from seq-input-gelf.

A few months on, has there been any movement on this? We're in a very similar situation to Luscit where we need to transmit GELF from a k8s cluster (in AKS) to Seq (on-prem) and would rather avoid plaintext-sending all of that traffic.

from seq-input-gelf.

Thanks for the ping @rjhenry. No movement yet, but seems like we should start assembling a plan.

Getting a certificate into sqelf is the first problem to deal with, I think. Are you running it as an input (Seq.Input.Gelf), or as a container (datalust/sqelf)?

from seq-input-gelf.

We're running as a container, so can trivially mount in certificate files.

from seq-input-gelf.

👍 thanks for your reply. Thinking about this some more, if sqelf accepted a certificate file path, and an (optional) certificate file password through regular app settings, this should work in both the app and container deployment configurations.

We'll aim to loop back around to this as soon as possible.

from seq-input-gelf.