Hi, I would rather advise to not reinvent the wheel of tcp communication but implement some simplistic mqtt appender that transports log events as json serialized messages.
In combination with a broker like mosquitto it provides secure communication, temporary peristent storage and many more advantages of pub/sub systems like multiple log event consumers and such. Cheers -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Tue, Jun 29, 2021, 20:46 Gary Gregory <garydgreg...@gmail.com> wrote: > FWIW, we use the server at work to listen to JSON log events. There is > definitely value there. > > Gary > > On Tue, Jun 29, 2021, 13:29 Ralph Goers <ralph.go...@dslextreme.com> > wrote: > > > Right now the server is more or less a sample we expect you will want to > > copy and modify, > > so releasing it doesn’t have a lot of value. > > > > On the “Online Drinks” call this weekend I mentioned that I had been > asked > > about being > > able to send logs from mobile devices to a backend collector securely > > (https with OAuth > > tokens). I’ve been thinking about enhancing the server to be able to > > support this kind of > > stuff as well as being able to provide something similar to JSON Template > > Layout to > > deserialize the log events. > > > > If that happens then I would expect the server would be something we > would > > want to > > release and formally support. > > > > Ralph > > > > > On Jun 29, 2021, at 8:29 AM, КонÑ�тантин Кракович < > > kosto....@gmail.com> wrote: > > > > > > Hi Team, > > > > > > Could you please let me know if you have plans to release TCP server > > from logging-log4j-tools project? > > > > > > > > > Best regards, > > > Kostyantyn > > > > > > > > > >
