The Flume appender can persist messages within the same process to files before sending them to other agents. I don't think any other appender can guarantee that.

Personally, I've been using direct console appenders lately and using graylog to slurp stdout on docker containers, but I'm not the one who set all that up. Either way, the most reliable way to log things outside of files is Flume.

On 3 April 2017 at 19:45, Gary Gregory <garydgregory@gmail.com> wrote:
Wait a sec. A JMS provider can guarantee message delivery. How can events be lost once they are in the provider? Are you saying that using an async logger is 'unsafe' because the events in the ring buffer go away if the JVM goes down?

Ideally I want to publish and forget, with the publish part asynchronous, call the API, and it returns right away.

Is there no way to do that with our JMS Appender?

Gary

On Mon, Apr 3, 2017 at 5:38 PM, Ralph Goers <ralph.goers@dslextreme.com> wrote:
What’s the point though when all you have to do is specify the pattern layout with “%m%ex{none}”?

How can you do auditing with the async logger? You may lose events with that.

Your use case is exactly why I wrote the FlumeAppender. It is very much like JMS but a whole lot faster and guarantees events aren’t lost.

Ralph

On Apr 3, 2017, at 5:03 PM, Gary Gregory <garydgregory@gmail.com> wrote:

Right. I want to post to JMS message objects I've serialized to JSON. All I care about is the message.

I log these events to a specially named logger with a specially named marker. These are the only events that should be published to JMS (I use a filter and the one marker). I am in charge of the message format and it is consumed on the other JMS side by a specialized agent which I also control.

IOW, I am using the Log4j infrastructure as the simplest way to send custom messages over to JMS. These are not traditional logging events, rather a kind of auditing system. I leverage the Log4j async logger as well. No need to deal with the JMS API.

Gary

On Mon, Apr 3, 2017 at 4:07 PM, Remko Popma <remko.popma@gmail.com> wrote:
So, exceptions are swallowed and no newlines are rendered? Interesting. 
What's the use case?

Sent from my iPhone

On Apr 4, 2017, at 7:30, Gary Gregory <garydgregory@gmail.com> wrote:

Hi All,

I am considering a new layout called "MessageLayout" which would be synonymous with:<PatternLayout pattern="%m" />. Thoughts? 




--




--



--
Matt Sicker <boards@gmail.com>