You can check the current status of Node Manager and use Node Manager logs to help troubleshoot problems in starting or stopping individual Managed Servers.

1. In the Monitoring Tree, go to Environment, then Node Manager Logs.
2. Click the name of the machine whose Node Manager logs you want to view.
3. Click Download.

A server can monitor key aspects of its subsystems and report when a subsystem is not functioning properly.

1. In the Edit Tree, go to Environment, then Servers, then myServer.
2. On the Health tab, modify the options as necessary.
3. Click Save.

In dashboards, filters are the criteria that you use to curate your results. Generally, filters are based on the properties of a node.

WebLogic Remote Console restricts which filters are available based on your current node so you can focus on the criteria that is relevant to your goals. As such, the filters that are available on the Environments: Servers node are different than those available under Deployments: Application Runtime Data.

Each filter consists of a name (or property) from the domain, a value, and an operator that determines how the name and value interact with each other. A basic dashboard filter is simply name=value. The following example dashboard filter returns any servers that require a restart to apply configuration changes:

ServerRuntime.RestartRequired == true

Values come in three formats:

• Text
• Numeric
• Boolean (expressed as option toggles). Set the option to On for True, Off for False.

Use operators to determine how a value should be assessed. Only the operators that are applicable to a name or property appear as options - you won't see greater than for text values. By default, all filters are set to Any to provide the broadest possible search parameters.

Dashboards consist of one or more filters and filters are cumulative - beans must match ALL of the defined filters to be returned as a result. Therefore, when you build a dashboard, only edit the filters that are relevant to your query and leave the rest of the filters unchanged.

WebLogic Remote Console provides a set of pre-defined dashboards to monitor common domain statistics.

You can create your own custom dashboards to monitor the state of your domain.

1. In the Monitoring Tree, go to the node in the Navigation Tree that most closely matches the type of content that you want to track. For example, if you want to learn about servers, open the Environment: Servers node.
2. Click New Dashboard.
3. Enter a name for your new dashboard and then begin configuring the filters that will determine the results of the dashboard. For guidance on how to build filters, see Dashboard Filters.
4. Click Create to generate the dashboard.
5. Optional: Click Customize Table to control which columns appear in the dashboard.

Each subsystem within WebLogic Server generates log messages to communicate its status. To keep a record of the messages that its subsystems generate, WebLogic Server writes the messages to log files.

1. In the Monitoring Tree, go to Diagnostics, then Logs and Archives.
2. Each row is a type of diagnostic data. Click on the row that you're interested in to view its logs.
3. Select a log file and then click Download Logs.
   Logs are segregated by server instance.

WebLogic Server generates log files to track and communicate the status of its various subsystems. To ensure these log files remain valuable and usable, you can configure their settings.

1. In the Edit Tree, go to Environment, then Servers, then myServer.
2. Click the Logging tab.
3. Modify the logging settings to suit your needs.
4. Click Save.
5. Repeat on the rest of the servers.
6. Go to Environment, then Domain.
7. Click the Logging tab.
8. Modify the settings for the domain-level log to suit your needs.
9. Click Save.

Specify debugging settings for WebLogic Server.

1. In the Edit Tree, go to Environment, then Servers, then myServer.
2. Click the Debug tab.
   The Debug tab is split into several subtabs that group related debug flags together. Use the All tab to see all available debug flags.
3. Enable the debug flags that you want to generate logging messages.
4. Click Save.

WebLogic Server can generate a significant amount of data in its log messages. You can filter log messages so only certain messages are published.

1. In the Edit Tree, go to Environment, then myServer.
2. Click on the Logging tab.
3. Click Show Advanced Fields.
4. If you want to change the default severity level for all loggers or packages in the logger tree, then choose a new level from the Minimum severity to log drop-down list.
   The default level is Info. For information on message severity, see Message Severity in Configuring Log Files and Filtering Log Messages for Oracle WebLogic Server.
5. If you want to redirect the standard out of the JVM in which the WebLogic Server instance runs to the four log message destinations (log file, standard out, domain log, and message buffer), then turn on Redirect stdout logging enabled. For more information, see Redirecting JVM Output in Configuring Log Files and Filtering Log Messages for Oracle WebLogic Server.
6. If you want to override the setting for the root Logger (as specified by the Minimum severity to log list option) or its closest parent node in the logger tree, then do as follows:
   1. Click the Severity Properties tab.
   2. In the Logger Severity Properties table, click + to add a new key-value row, then double-click the row cells to update the key and value.

   You can also use Logger severity properties to specify severity levels for packages (if using the Commons Logging API) or for individual WebLogic Server subsystem Loggers (if using the Message Catalog Logger).

   All loggers inherit the severity level of their nearest parent node in the logger hierarchy. You can specify a severity level for a given logger that is different than its nearest parent node using key-value pairs, where the key is the logger name and the value is the severity level (Info, Critical, Warning, and so on).

   See Specifying Severity Level for Loggers in Configuring Log Files and Filtering Log Messages for Oracle WebLogic Server.

7. If you want to control which log messages are published, you can create log filters which use custom logic to evaluate log message content and then accept or reject it for publication based on its criteria. You can apply log filters to these log message destinations: log file, standard out, and domain log broadcaster.
   1. Create a Log Filter.
   2. To apply a log filter to the log file message destination, choose your preferred severity level from the Log File Severity Level drop-down list, then choose a log filter from the Log File Filter drop-down list.
   3. To apply a log filter to the standard out message destination, choose your preferred severity level from the Stdout Severity Level drop-down list, then choose a log filter from the Stdout Filter drop-down list.
   4. To apply a log filter to the domain log broadcaster message destination, choose your preferred severity level from the Domain Log Broadcast Severity Level drop-down list, then choose a log filter from the Domain Log Broadcast Filter drop-down list.
      You can specify the size of the message buffer which stores messages that will be forwarded to the domain log. A higher value causes more messages to be stored in the buffer before the contents are forwarded to the domain log. For performance reasons, it is recommended that this value be set to 10 or higher in production mode.
   You cannot forward DEBUG messages to the domain log.
8. Click Save.

Log filters provide control over the log messages that get published. A filter uses custom logic to evaluate the log message content, which you use to accept or reject a log message

1. In the Edit Tree, go to Environment, then Log Filters.
2. Click New.
3. Enter a name for the log filter and click Create.
4. Enter an expression in the Filter Expression field.
   A filter expression defines simple filtering rules to limit the volume of log messages written to a particular log destination. For information on building filter expressions, see WLDF Query Language in Configuring and Using the Diagnostics Framework for Oracle WebLogic Server.
5. Click Save.

Set a rotation schedule for the log files generated by WebLogic Server.

1. In the Edit Tree, go to Environment, then Servers, then myServer.
2. On the Logging tab, from the Rotation Type drop-down list, select the criteria that triggers the server to move log messages to a separate file. Depending on your choice, configure the appropriate settings.
   • By Size - rotates log messages when log file size reaches the specified size.
   • By Time - rotates log messages after a specified time interval passes.
   • By Size or Time - rotates log messages if the file size reaches the specified size or if the specified time interval passes, whichever occurs first.
   • None - log messages are not automatically rotated. You must manually erase the contents of the file when the size becomes too large.
3. If you chose By Size as the Rotation Type.
   1. In the Rotation file size field, enter the file size that triggers the server to move log messages to a separate file. After the log file reaches the specified size, the next time the server checks the file size it renames the current log file by appending a 5-digit integer; for example, SERVER_NAME.log00007. After the server renames the file, subsequent messages accumulate in a new file named SERVER_NAME.log.
4. If you chose By Time as the Rotation Type.
   1. In the Begin rotation time field, enter the start time
      Use the following format: hh:mm, where hh is the hour in a 24-hour format and mm is the minute. At the time that you specify, the server rotates the current log file. If the time that you specify is already past, the server rotates the log file at the next scheduled interval, as specified in Rotation Interval.
   2. In the Rotation Interval field, enter the interval, in hours, at which the server saves old messages to another file.
5. If you chose By Size or Time as the Rotation Type, then configure the By Size and By Time options as described in steps 3 and 4.
6. Optional: If you want to limit the number of log files that the server creates to store old log messages, enable the Limit Number of Retained Log Files option. Then, in the Files to Retain field, enter the maximum number of files. If the server receives additional log messages after reaching the capacity of the last log file, it overwrites the oldest log file.
7. In the Log file rotation directory field, enter the directory location where the rotated log files will be stored.

   Enter an absolute pathname or a pathname that is relative to the server's root directory. By default, the rotated files are stored in the same directory where the log file is stored.

8. Optional: If you want to add a time or date stamp to the file name when the log file is rotated, then in the Log file name field, add java.text.SimpleDateFormat variables to the file name and surround each variable with percentage (%) characters.

   For example, if you enter the following value in the Log file name field: myserver_%yyyy%_%MM%_%dd%_%hh%_%mm%.log, the server's log file will be named myserver_yyyy_MM_dd_hh_mm.log.

   When the server instance rotates the log file, the rotated file name contains the date stamp. For example, if the server instance rotates its local log file on 4 March 2020 at 10:15 AM, the log file that contains the old log messages will be named myserver_2020_03_04_10_15.lognnnnn. (The current, in-use server log file retains the name myserver_yyyy_MM_dd_hh_mm.log.)

   If you do not include a time and date stamp, the rotated log files are numbered in order of creation SERVER_NAME.lognnnnn, where SERVER_NAME is the name configured for the log file. For example: myserver.log00007.

9. Click Save.

WebLogic Server supports configuring java.util.logging.Logger levels for named loggers in the JDK LogManager.

• To configure java.util.logging.Logger levels for the WebLogic Server logging configuration (also known as platform loggers):

  WebLogic Server loggers are configured in terms of weblogic.logging.Severities through the LoggerSeverities attribute. These loggers are not available in the JDK's default global LogManager.

  1. In the Edit Tree, go to Environment, then Servers, then myServer.
  2. Click the Logging tab.
  3. On the Platform Logger Levels subtab, click + to add a new row. Then, enter the logging level name under the Properties Name column and the logging level under Properties Value column.
  4. Click Save.
• To configure java.util.logging.Logger levels for Desktop WebLogic Remote Console:
  1. Go to File, then Settings. (On macOS, go to WebLogic Remote Console, then Settings.)
  2. Under the Logging/Debugging section, click + to add a new row and enter the logging level as a name-value pair, separated by =.
  3. Click Save.