Applies To:

Show Versions Show Versions

Manual Chapter: About log level configuration
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Log levels can be configured in various ways that depend on the specific functionality. Log levels for access portal traffic are configured in the System area of the product. The log level for the URL database download is configured in the default-log-setting in the Access > Overview > Event Log > Settings area of the product. The log level for NTLM authentication of Microsoft Exchange clients is configured using the ECA option in any log setting. Other access policy (and Secure Web Gateway) log levels are configured in any log setting.

Updating the log level for NTLM for Exchange clients

Before you follow these steps, you must have an access profile that you configured to use for NTLM authentication of Microsoft Exchange clients. You must know the name of the log setting that is assigned to that access profile. (The default-log-setting is assigned by default, but your access profile configuration might be different.)
You can change the level of logging for NTLM authentication for Microsoft Exchange clients.
Note: Logging at the default level, Notice, is recommended.
  1. On the Main tab, click Access > Overview > Event Logs > Settings .
    A log settings table screen opens.
  2. Select the check box for the log setting that you want to update and click Edit.
    A popup screen opens.
  3. To configure settings for access system logging, select Access System Logs from the left pane.
    Access System Logs settings display in the right panel.
  4. For the ECA setting, select a log level.
    Note: Setting the log level to Debug can adversely impact system performance.
  5. Click OK.
    The popup screen closes.

Configuring logging for the URL database

Configure logging for the URL database so that log messages are published to the destinations, and at the minimum log level, that you specify. (Logging for the URL database occurs at the system level, not the session level, and is controlled using the default-log-setting log setting.)
Note: A URL database is available only on a BIG-IP® system with an SWG subscription.
  1. On the Main tab, click Access > Overview > Event Logs > Settings .
    A log settings table screen opens.
  2. From the table, select default-log-setting and click Edit.
    A log settings popup screen displays.
  3. Verify that the Enable access system logs check box is selected.
  4. To configure settings for access system logging, select Access System Logs from the left pane.
    Access System Logs settings display in the right panel.
  5. From the Log Publisher list, select the log publisher of your choice.
    A log publisher specifies one or more logging destinations.
    Important: The BIG-IP® system is not a logging server and has limited capacity for storing, archiving, and analyzing logs. For this reason a dedicated logging server is recommended.
  6. To change the minimum log level, from the Secure Web Gateway list, select a log level.
    Note: Setting the log level to Debug can adversely impact system performance.
    The default log level is Notice. At this level, logging occurs for messages of severity Notice and for messages at all incrementally greater levels of severity.
  7. Click OK.
    The popup screen closes. The table displays.

Setting log levels for Portal Access and VDI events

Change the logging level for access policy events when you need to increase or decrease the minimum severity level at which Access Policy Manager® (APM®) logs that type of event. Follow these steps to change the log level for events that are related to portal access traffic or related to connections to virtual desktops (VDI).

Note: You can configure log levels for additional APM options in the Event Logs area.
  1. On the Main tab, click System > Logs > Configuration > Options .
  2. Scroll down to the Access Policy Logging area.
    The options Portal Access and VDI display; each displays a selected logging level.
    Note: The log settings that you change on this page impact only the access policy events that are logged locally on the BIG-IP® system.
  3. For each option that you want to change, select a logging level from the list.
    Note: Setting the log level to Debug affects the performance of the BIG-IP® system.
    Warning: F5® recommends that you do not set the log level for Portal Access to Debug. Portal Access can stop working. The BIG-IP system can become slow and unresponsive.
  4. Click Update.
APM starts to log events at the new minimum severity level.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)