Log4net
  1. Log4net
  2. LOG4NET-259

Log4Net does not create a new tab in Chainsaw

    Details

    • Type: Task Task
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 1.2.10
    • Fix Version/s: 1.2.12
    • Component/s: Documentation
    • Labels:
      None

      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.

        Activity

        David Mackersie created issue -
        David Mackersie made changes -
        Field Original Value New Value
        Issue Type Bug [ 1 ] Task [ 3 ]
        Priority Major [ 3 ] Minor [ 4 ]
        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
        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.
        Component/s Documentation [ 11604 ]
        Component/s Other [ 11606 ]
        Stefan Bodewig made changes -
        Fix Version/s 1.2 Maintenance Release [ 12317606 ]
        Dominik Psenner made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Assignee Dominik Psenner [ nachbarslumpi ]
        Fix Version/s 1.2 Maintenance Release [ 12317606 ]
        Resolution Fixed [ 1 ]
        Dominik Psenner made changes -
        Fix Version/s 1.2.12 [ 12318546 ]

          People

          • Assignee:
            Dominik Psenner
            Reporter:
            David Mackersie
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development