created LOG4J2-1865:
Summary: Many Issues with SyslogAppender: Unable to Send Stack
Traces Over SyslogAppender using TCP, AppenderComponentBuilder lacks
LoggerFields
Key: LOG4J2-1865
URL: https
ssue:
https://github.com/apache/logging-log4j2/pull/46
LOG4J2-969 was closed. Is this patch still necessary?
> Refactor SyslogAppender so that Layout is a Plugin element
> ---
>
> Key: LOG4J2-969
>
Thanks Matt!
Sam, can you check if this resolves the issue?
Sent from my iPhone
> On Feb 4, 2017, at 14:49, Matt Sicker wrote:
>
> I see. There were a couple issues with @PluginAliases for SyslogAppender
> specifically. Fixed in master.
>
>> On 3 February 2017 at 10:2
I see. There were a couple issues with @PluginAliases for SyslogAppender
specifically. Fixed in master.
On 3 February 2017 at 10:23, Matt Sicker wrote:
> Plugins can have aliases via @PluginAliases (see for example <
> https://github.com/apache/logging-log4j2/blob/master/
> log4j-c
gt;
>> It appears that change was part of this commit:
>>
>> commit ed828be67a23ee3513cafc9d2fd0ff16a26c7013
>> Author: Gary Gregory
>> Date: Mon Nov 14 15:11:47 2016 -0800
>>
>> [LOG4J2-1709]
>>
>> Add a Builder
following error:
>
> ERROR Syslog contains an invalid element or attribute
> "reconnectionDelayMillis"
>
>
> It appears that change was part of this commit:
>
> commit ed828be67a23ee3513cafc9d2fd0ff16a26c7013
> Author: Gary Gregory
> Date: Mon Nov 14
> It appears that change was part of this commit:
>
> commit ed828be67a23ee3513cafc9d2fd0ff16a26c7013
> Author: Gary Gregory
> Date: Mon Nov 14 15:11:47 2016 -0800
>
> [LOG4J2-1709]
>
> Add a Builder to SyslogAppender and deprecate
> S
t:
commit ed828be67a23ee3513cafc9d2fd0ff16a26c7013
Author: Gary Gregory
Date: Mon Nov 14 15:11:47 2016 -0800
[LOG4J2-1709]
Add a Builder to SyslogAppender and deprecate
SyslogAppender.createAppender().
The documentation (https://logging.apache.org/lo
g4j/2.x/manual/appe
}} element for a
{{SyslogAppender}} which will override the {{format}} setting.
> Refactor SyslogAppender so that Layout is a Plugin element
> ---
>
> Key: LOG4J2-969
> URL: https://issues.apache.
[
https://issues.apache.org/jira/browse/LOG4J2-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory reopened LOG4J2-969:
-
Assignee: Gary Gregory
> Refactor SyslogAppender so that Layout is a Plugin elem
Add a Builder to SyslogAppender and deprecate SyslogAppender.createAppender().
> --
>
> Key: LOG4J2-1709
> URL: https://issues.apache.org/jira/browse/LOG4J2-1709
>
Gary Gregory created LOG4J2-1709:
Summary: Add a Builder to SyslogAppender and deprecate
SyslogAppender.createAppender().
Key: LOG4J2-1709
URL: https://issues.apache.org/jira/browse/LOG4J2-1709
sage:
This closes #46
commit d0882fab96f9fcaa2764a3c6d5348b2fe7005f8e
Author: Dominique Villard
Date: 2016-10-05T13:25:00Z
add configurable syslog layout
> Refactor SyslogAppender so that Layout is a Plugin
oned above, is the TAG field
being logged by log4j2?
i.e. If my xml uses
and my slf4j logger writes "app msg1 msg2 msg3" using log4j2, I only see "msg1
msg2 msg3" in syslog?
> Refactor SyslogAppender so that
ased (probably from before
2.0-alpha1 even). Strange that this issue would have been reported in the first
place, then.
> Parameter of mdcId in SyslogAppender has no default value.
> --
>
> Key: LOG4J2-922
>
[
https://issues.apache.org/jira/browse/LOG4J2-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory closed LOG4J2-969.
---
Resolution: Workaround
Closing as "Workaround" (see comments).
> Refactor SyslogApp
eNewLine = includeNL == null ? false :
Boolean.valueOf(includeNL);
+if (mdcId == null) {
+mdcId = DEFAULT_MDCID;
+}
return new RFC5424Layout(f, id, enterpriseNumber, isMdc,
includeNewLine, mdcId, appName, msgId, excludes,
- include
rsion.
> Parameter of mdcId in SyslogAppender has no default value.
> --
>
> Key: LOG4J2-922
> URL: https://issues.apache.org/jira/browse/LOG4J2-922
> Project: Log4j 2
>
quot;newLineEscape") final String escapeNL,
@PluginAttribute(value = "charset", defaultString = "ISO-8859-1")
final Charset charset,
@PluginAttribute(value = "pattern") String patter
ix for the facility/priority I
need. Hacky but it seems to work.
But for this kind of issue I think maybe allowing chained layouts or something
would help. Syslog appender could actually just add a messageLayout element
that could be a pattern that does the initial formatting.
> Refactor Sysl
cket layout?
> Refactor SyslogAppender so that Layout is a Plugin element
> ---
>
> Key: LOG4J2-969
> URL: https://issues.apache.org/jira/browse/LOG4J2-969
> Project: Log4j 2
d syslog/remote) but also use the regex inside to mask credit card
numbers.
> Refactor SyslogAppender so that Layout is a Plugin element
> ---
>
> Key: LOG4J2-969
> URL: http
ot; is to just use the SocketAppender with a
Layout.
> Refactor SyslogAppender so that Layout is a Plugin element
> ---
>
> Key: LOG4J2-969
> URL: https://issues.apache.org/jira/browse/LOG
iguration examples was all you needed?
> Refactor SyslogAppender so that Layout is a Plugin element
> ---
>
> Key: LOG4J2-969
> URL: https://issues.apache.org/jira/browse/LOG4J2-969
>
outs.
> Refactor SyslogAppender so that Layout is a Plugin element
> ---
>
> Key: LOG4J2-969
> URL: https://issues.apache.org/jira/browse/LOG4J2-969
> Project: Log4j 2
>
[
https://issues.apache.org/jira/browse/LOG4J2-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-969:
Summary: Refactor SyslogAppender so that Layout is a Plugin element (was:
Refactor SyslogAppender
yslog appender?
Can you recommend any way to accomplish custom body messages in SyslogAppender,
just through configuration files?
@paul, could you share your custom BsdLayout?
was (Author: micpalmia):
I also need to format the body part of the Syslog message and I'm quite
frustrated by how ha
yslog appender?
Can you recommend any way to accomplish custom body messages in SyslogAppender,
just through configuration files?
@paul, could you share your custom BsdSyslogLayout?
was (Author: micpalmia):
I also need to format the body part of the Syslog message and I'm quite
frustrated by
omplish custom body messages in SyslogAppender,
just through configuration files?
> Refactor SyslogAppender so that Layout is an PluginElement
> --
>
> Key: LOG4J2-969
> URL: https://issues.apac
dcId is missing in documentation of SyslogAppender
> -
>
> Key: LOG4J2-1072
> URL: https://issues.apache.org/jira/browse/LOG4J2-1072
> Project: Log4j 2
> Issue Type:
Martin Schröder created LOG4J2-1072:
---
Summary: Parameter mdcId is missing in documentation of
SyslogAppender
Key: LOG4J2-1072
URL: https://issues.apache.org/jira/browse/LOG4J2-1072
Project: Log4j 2
the failover mechanism. Good catch!
> When SyslogAppender can't find inetAddress at startup, it will never try to
> reconnect
> -
>
> Key: LOG4J2-1047
> URL: htt
pender to kick in...
Fun stuff. Requires more thought.
> When SyslogAppender can't find inetAddress at startup, it will never try to
> reconnect
> -
>
> Key: LOG4J2-1047
ata.immediateFail, data.layout);
}
}
--
1.9.1
{code}
> When SyslogAppender can't find inetAddress at startup, it will never try to
> reconnect
> -
>
> Key: LOG4J2-1047
file that applies cleanly on top of Git
master?
> When SyslogAppender can't find inetAddress at startup, it will never try to
> reconnect
> -
>
> Key: LOG4J2-1047
>
the middle of an app is a different issue. It
does seem like some kind of configurable timeout should kick-in. Whatever
solution should also work with the failover appender.
> When SyslogAppender can't find inetAddress at startup, it will never try to
server which is receiving the messages.
Actually it feels like when some buffer is full, then the timeout isn't
respected.
Is it an issue you're aware of? Should I open another ticket?
> When SyslogAppender can't find inetAddre
etAddress, the behavior is exactly the same as before. (The rest of the patch
is just plumbing).
So, in the scenario you describe, since we launch the program with the network
on, then the InetAddress is derived since the beginning, so the behavior isn&#x
t; When SyslogAppender can't find inetAddress at startup, it will never try to
> reconnect
> -
>
> Key: LOG4J2-1047
> URL: https://issues.apache.
[
https://issues.apache.org/jira/browse/LOG4J2-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-1047:
-
Summary: When SyslogAppender can't find inetAddress at startup, it will
never try to reco
[
https://issues.apache.org/jira/browse/LOG4J2-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-969:
Summary: Refactor SyslogAppender so that Layout is an PluginElement (was:
Refactor syslogappender
Appender instead together with our own BsdSyslogLayout to
solve our needs. Thank you for the tip! Maybe add to the log4j2 SyslogAppender
documentation that the following are equivalent:
|{code}
own BsdSyslogLayout to
solve our needs. Thank you for the tip! Maybe add to the log4j2 SyslogAppender
documentation that the following are equivalent:
|{code}
{code}|{code}
eady seems like it was answered
correctly.
The SyslogAppender does not accept arbitrary layouts because it is intended to
conform to either the original syslog format or RFC 5424. No other Layout
should be permitted.
The SyslogAppender is really nothing more than the SocketAppender with one of
t
MDC (thread context) data to the old
BSD formats. So I was going to create my own BsdSyslogLayout class that has a
pattern (like the PatternLayout). The way the code is now, the SyslogAppender
layout parameter is not extendable at all. (The new log4j2 plugin system is
brilliant by the way!) Further
orce all current users to rewrite
their config files? I suppose you could add a layout argument and use that as
an alternative until we want to impose the pain of telling users to rewrite
config files.
> Refactor syslogappender so that Layout is an Plugin
the protocol of SyslogAppender is SSL
and the layout is of type RFC5424 does not have useTlsMessageFormat=true.
> Refactor syslogappender so that Layout is an PluginElement
> --
>
> Key: LOG4J2-969
>
Paul D Johe created LOG4J2-969:
--
Summary: Refactor syslogappender so that Layout is an PluginElement
Key: LOG4J2-969
URL: https://issues.apache.org/jira/browse/LOG4J2-969
Project: Log4j 2
Issue
[
https://issues.apache.org/jira/browse/LOG4J2-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angus.aqlu updated LOG4J2-922:
--
Affects Version/s: (was: 2.1)
> Parameter of mdcId in SyslogAppender has no default va
[
https://issues.apache.org/jira/browse/LOG4J2-922?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angus.aqlu updated LOG4J2-922:
--
Fix Version/s: (was: 2.2)
> Parameter of mdcId in SyslogAppender has no default va
angus.aqlu created LOG4J2-922:
-
Summary: Parameter of mdcId in SyslogAppender has no default value.
Key: LOG4J2-922
URL: https://issues.apache.org/jira/browse/LOG4J2-922
Project: Log4j 2
Issue
ate docs for SyslogAppender: "No structured id name was supplied"
>
>
> Key: LOG4J2-901
> URL: https://issues.apache.org/jira/browse/LOG4J2-901
> Project: Log4j
[
https://issues.apache.org/jira/browse/LOG4J2-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-901:
Summary: Update docs for SyslogAppender: "No structured id name was
supplied" (was: Sysl
tion is not up-to-date. A mdcId is needed in the xml
config. Answer can be found here:
http://stackoverflow.com/questions/26978520/log4j2-syslogappender-not-working/27024698#27024698
> SyslogAppender not working - "No structured id name
[
https://issues.apache.org/jira/browse/LOG4J2-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tihomir Meščić updated LOG4J2-901:
--
Summary: SyslogAppender not working - "No structured id name was supplied&qu
Tihomir Meščić created LOG4J2-901:
-
Summary: SyslogAppender not working
Key: LOG4J2-901
URL: https://issues.apache.org/jira/browse/LOG4J2-901
Project: Log4j 2
Issue Type: Bug
1 AM:
---
In git master.
The new appender takes a new parameter {{connectTimeoutMillis}}.
was (Author: garydgregory):
In git master.
> Specify the SyslogAppender connect timeout value as part of the config
[
https://issues.apache.org/jira/browse/LOG4J2-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory resolved LOG4J2-895.
-
Resolution: Fixed
Fix Version/s: 2.2
In git master.
> Specify the SyslogAppender conn
[
https://issues.apache.org/jira/browse/LOG4J2-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated LOG4J2-895:
Summary: Specify the SyslogAppender connect timeout value as part of the
configuration (was
ed a more immediate fix. - Sam
> Specify the SyslogAppender timeout value as part of the configuration
> -
>
> Key: LOG4J2-895
> URL: https://issues.apache.org/jira/browse/LOG4J2-895
>
[
https://issues.apache.org/jira/browse/LOG4J2-895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory reassigned LOG4J2-895:
---
Assignee: Gary Gregory
> Specify the SyslogAppender timeout value as part of
the SyslogAppender doesn't provide a way to override the default
socket timeout. This resulted in my application noticeably hanging on startup
when waiting for the socket to timeout.
As a short term fix I created an extension largely based on the SyslogAppender
that includes the conne
ps is unavailable. My work around is to always also include an appender that
I know to be available.
I've got a SyslogAppender that sends logs to a remote EC2 box and I've wrapped
it in an AsyncAppender. The log traffic's is just to monitor the state of the
application and it&#
nder? That will make it clearer to
see what you want to do and if it works with your changes ;-)
Thank you!
Gary
> Specify the SyslogAppender timeout value as part of the configuration
> -
>
>
Sam Beroz created LOG4J2-895:
Summary: Specify the SyslogAppender timeout value as part of the
configuration
Key: LOG4J2-895
URL: https://issues.apache.org/jira/browse/LOG4J2-895
Project: Log4j 2
Sam Beroz created LOG4J2-894:
Summary: AsyncAppender throws ConfigurationException when wrapped
SyslogAppender fails
Key: LOG4J2-894
URL: https://issues.apache.org/jira/browse/LOG4J2-894
Project: Log4j 2
https://issues.apache.org/bugzilla/show_bug.cgi?id=35743
--- Comment #7 from Jackie Rosen ---
*** Bug 260998 has been marked as a duplicate of this bug. ***
Seen from the domain http://volichat.com
Page where seen: http://volichat.com/adult-chat-rooms
Marked for reference. Resolved as fixed @bugz
[
https://issues.apache.org/jira/browse/LOG4J2-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Benke updated LOG4J2-338:
---
Attachment: documentation_notes.patch
> Add TLS support to SyslogAppen
the documentation and I'm going to attach the patch.
> Add TLS support to SyslogAppender
> -
>
> Key: LOG4J2-338
> URL: https://issues.apache.org/jira/browse/LOG4J2-338
> Project: Log4j 2
(mainly missing license headers,
missing javadoc and doc, and integration with other changes that had been
committed). Please verify and close.
> Add TLS support to SyslogAppender
> -
>
> Key: LOG4J2-338
>
mods, please see that ticket. I added a few
questions on related code to that issue as well.
Gary
> Add TLS support to SyslogAppender
> -
>
> Key: LOG4J2-338
> URL: https://issues.apache.org/jir
t to wait until LOG4J2-355 will be
applied, because it will broke again this patch and I don't want to recreate it
too many times.
> Add TLS support to SyslogAppender
> -
>
> Key: LOG4J2-338
> URL: h
ting. All the files were missing
license headers and I have to fix some checkstyle issues and create some
documentation.
> Add TLS support to SyslogAppender
> -
>
> Key: LOG4J2-338
> URL: https://iss
the current version of trunk please?
Thank you,
Gary
> Add TLS support to SyslogAppender
> -
>
> Key: LOG4J2-338
> URL: https://issues.apache.org/jira/browse/LOG4J2-338
> Project: Log4j 2
the log4j2 contained this feature in
the GA release.
> Add TLS support to SyslogAppender
> -
>
> Key: LOG4J2-338
> URL: https://issues.apache.org/jira/browse/LOG4J2-338
> Project: Log4j 2
It contains the patch, the certificates to test and a sample log4j2.xml
configuration.
> Add TLS support to SyslogAppender
> -
>
> Key: LOG4J2-338
> URL: https://issues.apache.org/jir
log4j2.xml
configuration.
> Add TLS support to SyslogAppender
> -
>
> Key: LOG4J2-338
> URL: https://issues.apache.org/jira/browse/LOG4J2-338
> Project: Log4j 2
> Is
Tibor Benke created LOG4J2-338:
--
Summary: Add TLS support to SyslogAppender
Key: LOG4J2-338
URL: https://issues.apache.org/jira/browse/LOG4J2-338
Project: Log4j 2
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/LOG4J2-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ralph Goers closed LOG4J2-183.
--
> SyslogAppender and remote rsyslog ser
Hello,
I send Tomcat logs to a remote rsyslog server via a SyslogAppender.
My appender configuration is the following :
The rsyslog server receives correctly the Tomcat logs but the rsyslog $hostname
variable contains the IP address of the Tomcat
https://issues.apache.org/bugzilla/show_bug.cgi?id=54815
grobmeier changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.apache.org/bugzilla/show_bug.cgi?id=54815
--- Comment #1 from grobmeier ---
Hello
thanks for your question. We use Bugzilla only for issues, not for support.
Could you please subscribe to [email protected] (done with sending a
blank mail to: log4j-dev-subscr...@logging
https://issues.apache.org/bugzilla/show_bug.cgi?id=54818
Bug ID: 54818
Summary: SyslogAppender tag does not support non-alphanumeric
characters.
Product: Log4j
Version: 1.2.18
Hardware: PC
OS: Linux
https://issues.apache.org/bugzilla/show_bug.cgi?id=54815
Bug ID: 54815
Summary: SyslogAppender and remote rsyslog server
Product: Log4j
Version: 1.2
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Log4j 2.x.
> SyslogAppender and remote rsyslog server
>
>
> Key: LOG4J2-183
> URL: https://issues.apache.org/jira/browse/LOG4J2-183
> Project: Log4j 2
>
Eric Savidan created LOG4J2-183:
---
Summary: SyslogAppender and remote rsyslog server
Key: LOG4J2-183
URL: https://issues.apache.org/jira/browse/LOG4J2-183
Project: Log4j 2
Issue Type: Question
[
https://issues.apache.org/jira/browse/LOG4J2-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emanuele Colombo closed LOG4J2-101.
---
The problem is now solved. Thanks!
> Attribute "format" for Sysl
1400254. Please verify and close.
> Attribute "format" for SyslogAppender is mandatory
> --
>
> Key: LOG4J2-101
> URL: https://issues.apache.org/jira/browse/LOG4J2-101
>
Emanuele Colombo created LOG4J2-101:
---
Summary: Attribute "format" for SyslogAppender is mandatory
Key: LOG4J2-101
URL: https://issues.apache.org/jira/browse/LOG4J2-101
Projec
https://issues.apache.org/bugzilla/show_bug.cgi?id=46626
Mathieu Rozieres changed:
What|Removed |Added
URL|http://mrozieres.free.fr/de |https://issues.apache.org/b
https://issues.apache.org/bugzilla/show_bug.cgi?id=46626
Gary Gregory changed:
What|Removed |Added
Target Milestone|--- |1.2.18
--
You are receiving this m
https://issues.apache.org/bugzilla/show_bug.cgi?id=46626
Gary Gregory changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://issues.apache.org/bugzilla/show_bug.cgi?id=46626
Gary Gregory changed:
What|Removed |Added
Summary|Log4J SyslogAppender does |Log4J SyslogAppender does
https://issues.apache.org/bugzilla/show_bug.cgi?id=46626
--- Comment #7 from Steven Willis ---
(In reply to comment #6)
> Hi Steven,
>
> Thank you for the new patch.
>
> If APP-NAME is the current term, shouldn't the ivar be called 'appName'
> instead of 'tag'?
>
> Gary
Well, this class is s
https://issues.apache.org/bugzilla/show_bug.cgi?id=46626
--- Comment #6 from Gary Gregory ---
Hi Steven,
Thank you for the new patch.
If APP-NAME is the current term, shouldn't the ivar be called 'appName' instead
of 'tag'?
Gary
--
You are receiving this mail because:
You are the assignee f
https://issues.apache.org/bugzilla/show_bug.cgi?id=46626
Steven Willis changed:
What|Removed |Added
Attachment #28801|0 |1
is obsolete|
ages, for example:
http://tools.ietf.org/html/rfc5424 the TAG (now called APP-NAME) field has been
moved into the header. Because, frankly, it makes more sense there.
The problem is that when a stack trace is sent along with a log message, the
SyslogAppender sends each line of the stack trace as a s
https://issues.apache.org/bugzilla/show_bug.cgi?id=46626
--- Comment #3 from Gary Gregory ---
Hm... I also read:
"The TAG is a string of ABNF alphanumeric characters that MUST NOT exceed 32
characters."
This patch does not truncate the Java String.
Am I looking at the right spec?
--
You are
https://issues.apache.org/bugzilla/show_bug.cgi?id=46626
--- Comment #2 from Gary Gregory ---
I wonder if some of the code in the patch is in the wrong place.
In "4.1.3 MSG Part of a syslog Packet" from https://tools.ietf.org/html/rfc3164
I read:
"The MSG part has two fields known as the TAG f
holding
all conversation regarding this bug through bugzilla?
-Steven Willis
From: [email protected] [mailto:[email protected]]
Sent: Thursday, May 17, 2012 2:21 PM
To: [email protected]
Subject: [Bug 46626] Log4J SyslogAppender does not handle TAG correctly
Steven Willis<mailto:on
1 - 100 of 213 matches
Mail list logo
