Hi David,
- Original Message -
> On Wed, Dec 18, 2013 at 10:32 AM, Holger Winkelmann [TP]
> wrote:
> > with HTTP you need to setup another server and provide a "Call back URL"
>
> Folks seem to increasingly call this pattern "web hooks."
I know, but i tried to avoid to use the webish te
On Wed, Dec 18, 2013 at 10:32 AM, Holger Winkelmann [TP]
wrote:
> with HTTP you need to setup another server and provide a "Call back URL"
Folks seem to increasingly call this pattern "web hooks."
___
systemd-devel mailing list
systemd-devel@lists.freed
Hi,
- Original Message -
> On Wed, Dec 18, 2013 at 05:22:48PM +0100, Holger Winkelmann [TP] wrote:
> > means to send a message over HTTP which ends up in the journal, basically
> > the counterpart
> > of systems-journal.gatewayd?
> Yes.
cool, I'm not sooo sure about HTTP Transports works
On Wed, Dec 18, 2013 at 05:22:48PM +0100, Holger Winkelmann [TP] wrote:
> means to send a message over HTTP which ends up in the journal, basically the
> counterpart
> of systems-journal.gatewayd?
Yes.
> What do think is the best transport representation for
> remote logging:
>
> a) keep the bin
Hi
> > By writing distributed applications we will look further for log
> > aggregation in the style of the systems-journal-gateway.
> > Regarding this I would like to know about the idea and plans of
> > the systemd community. Following the emails about logger optimization
> > Lennart mentioned
On Wed, Dec 18, 2013 at 08:44:36AM +0100, Holger Winkelmann [TP] wrote:
> Hi all,
>
> we are following the discussion initiated by Cecil about systemd
> journal for a while. The last couple of weeks we have developed
> a Erlang adapter for the journal to allow structured native logging.
> Therefor
Hi all,
we are following the discussion initiated by Cecil about systemd
journal for a while. The last couple of weeks we have developed
a Erlang adapter for the journal to allow structured native logging.
Therefore we have developed a ejournald [1] backend for the Erlang
logging framework lager [
