Web Agent Guides › Web Agent Configuration Guide › Configure Logs › How to Set Up Trace Logging › Determine the Content of the Trace Log

Determine the Content of the Trace Log

The WebAgentTrace.conf file determines the content of the trace log. You can control which components and data items appear in your trace log by modifying the settings of the WebAgentTrace.conf file on your web server. The following considerations apply when editing the file:

• Entries are case-sensitive.

  When you specify a component, data field, or filter, the values must match exactly the options in the WebAgentTrace.conf file instructions.

• Uncomment the configuration settings lines or they will be ignored.
• If you modify the WebAgentTrace.conf file before installing a new Web Agent over an existing Web Agent, the file is overwritten. Therefore, you should rename or back up the file first. After the installation, you can integrate your changes into the new file.

To determine the content of the trace log

1. Open the WebAgentTrace.conf file.

   Note: We recommend duplicating the original file and making changes to the copy. This preserves the default settings.

2. Add components and subcomponents using the following steps:
   1. Find the section that matches your type of agent. For example, if you have an Apache 2.0 Web Agent installed on your server, look for a line resembling the following:

      # For Apache 2.0, Apache 2.2, IIS 6.0, IIS 7.0 and SunOne Web Agents
      

      The SiteMinder r12.0 SP2 IIS Web Agent is an ISAPI filter and extension, which operates on both IIS 6 and IIS 7. IIS 7 installations require additional role services on your web server before configuring the SiteMinder Web Agent.

      Note: For more information, see the SiteMinder Web Agent Installation Guide.

   2. Locate the following line in that section:

      #components:
      

   3. Uncomment the line (if it is still commented), and then add the component names you want after the colon. Separate multiple components commas as shown in the following example:

      components:  AgentFramework, HTTPAgent
      

   4. (Optional) Follow the component name with the name of a subcomponent you want. Separate the subcomponent name with a slash as shown in the following example:

      components:  AgentFramework/Administration
      

3. Add data fields and filters using the following steps:
   1. Locate the following line in the appropriate section:

      #data:
      

   2. Uncomment the line (if it is still commented), and then add the data fields you want after the colon. Separate multiple data fields with commas as shown in the following example:

      data: Date, Time, Pid, Tid, TransactionID, Function, Message, IPAddr
      

   3. (Optional) Add filters to your data fields by following the data field with a colon, the boolean operator and the value you want. The values you specify for the filters must match exactly. The following example shows a filter which logs activities for a specific IP address:

      data: Date, Time, Pid, Tid, TransactionID, Function, Message, IPAddr:==127.0.0.1
      

      Note: Each filter must be on a separate line in the file.

4. Save your changes and close the file.
5. Restart the web server to apply your changes.

   The content of the trace log has been determined.