You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4net-dev@logging.apache.org by "David Mackersie (JIRA)" <ji...@apache.org> on 2010/06/01 23:55:52 UTC
[jira] Updated: (LOG4NET-259) Log4Net does not create a new tab in
Chainsaw
[ https://issues.apache.org/jira/browse/LOG4NET-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Mackersie updated LOG4NET-259:
------------------------------------
Issue Type: Task (was: Bug)
Priority: Minor (was: Major)
Description:
I believe the problem is in XmlLayoutSchemaLog4j, and that you need to change "log4japp" to "application".
According to the Chainsaw tutorial:
Chainsaw automatically looks inside each received LoggingEvent for a special Application property to determine which tab to route an event to. If it cannot find this property, it attempts to use a secondary property usually added via the SocketAppender or SocketHubAppender which identify the remote host of these events. If neither of these are found, Chainsaw routes events to a default "Unknown" tab.
Logging events generated internally by chainsaw include the following properties:
<log4j:properties>
<log4j:data name="application" value="Generator 1"/>
<log4j:data name="hostname" value="localhost"/>
<log4j:data name="log4jid" value="2"/>
<log4j:data name="some string" value="some valueGenerator 1"/>
</log4j:properties>
Logging events generated by XmlLayoutSchemaLog4j include the following properties:
<log4j:properties>
<log4j:data name="log4net:UserName" value="DOMAIN\username"/>
<log4j:data name="log4jid" value="281"/>
<log4j:data name="log4jmachinename" value="machineName"/>
<log4j:data name="log4net:HostName" value="machineName"/>
<log4j:data name="log4japp" value="Application.exe"/>
</log4j:properties>
See also: http://www.mail-archive.com/log4j-dev@jakarta.apache.org/msg05361.html
UPDATE: Documentation issue. See comments below.
was:
I believe the problem is in XmlLayoutSchemaLog4j, and that you need to change "log4japp" to "application".
According to the Chainsaw tutorial:
Chainsaw automatically looks inside each received LoggingEvent for a special Application property to determine which tab to route an event to. If it cannot find this property, it attempts to use a secondary property usually added via the SocketAppender or SocketHubAppender which identify the remote host of these events. If neither of these are found, Chainsaw routes events to a default "Unknown" tab.
Logging events generated internally by chainsaw include the following properties:
<log4j:properties>
<log4j:data name="application" value="Generator 1"/>
<log4j:data name="hostname" value="localhost"/>
<log4j:data name="log4jid" value="2"/>
<log4j:data name="some string" value="some valueGenerator 1"/>
</log4j:properties>
Logging events generated by XmlLayoutSchemaLog4j include the following properties:
<log4j:properties>
<log4j:data name="log4net:UserName" value="DOMAIN\username"/>
<log4j:data name="log4jid" value="281"/>
<log4j:data name="log4jmachinename" value="machineName"/>
<log4j:data name="log4net:HostName" value="machineName"/>
<log4j:data name="log4japp" value="Application.exe"/>
</log4j:properties>
See also: http://www.mail-archive.com/log4j-dev@jakarta.apache.org/msg05361.html
Component/s: Documentation
(was: Other)
Changing the Chainsaw "tab identifier" field as described by Scott Deboy solves the issue.
This would be worth mentioning in the "How To" at: http://logging.apache.org/log4net/release/howto/chainsaw.html
> Log4Net does not create a new tab in Chainsaw
> ---------------------------------------------
>
> Key: LOG4NET-259
> URL: https://issues.apache.org/jira/browse/LOG4NET-259
> Project: Log4net
> Issue Type: Task
> Components: Documentation
> Affects Versions: 1.2.10
> Reporter: David Mackersie
> Priority: Minor
>
> I believe the problem is in XmlLayoutSchemaLog4j, and that you need to change "log4japp" to "application".
> According to the Chainsaw tutorial:
> Chainsaw automatically looks inside each received LoggingEvent for a special Application property to determine which tab to route an event to. If it cannot find this property, it attempts to use a secondary property usually added via the SocketAppender or SocketHubAppender which identify the remote host of these events. If neither of these are found, Chainsaw routes events to a default "Unknown" tab.
> Logging events generated internally by chainsaw include the following properties:
> <log4j:properties>
> <log4j:data name="application" value="Generator 1"/>
> <log4j:data name="hostname" value="localhost"/>
> <log4j:data name="log4jid" value="2"/>
> <log4j:data name="some string" value="some valueGenerator 1"/>
> </log4j:properties>
> Logging events generated by XmlLayoutSchemaLog4j include the following properties:
> <log4j:properties>
> <log4j:data name="log4net:UserName" value="DOMAIN\username"/>
> <log4j:data name="log4jid" value="281"/>
> <log4j:data name="log4jmachinename" value="machineName"/>
> <log4j:data name="log4net:HostName" value="machineName"/>
> <log4j:data name="log4japp" value="Application.exe"/>
> </log4j:properties>
> See also: http://www.mail-archive.com/log4j-dev@jakarta.apache.org/msg05361.html
> UPDATE: Documentation issue. See comments below.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.