1. RESTful Edit Management Interface for Oracle WebLogic Server
  2. Tasks
  3. Log
  4. Server Templates
  5. Log

Modify This Log

post

/management/weblogic/{version}/edit/serverTemplates/{name}/log

Modify this log.

Request

Supported Media Types
Path Parameters
Header Parameters
  • The 'X-Requested-By' header is used to protect against Cross-Site Request Forgery (CSRF) attacks. The value is an arbitrary name such as 'MyClient'.
Body ()

Must contain the modified log model.

Root Schema : Log
Type: object
Show Source
  • Default Value: 8

    Gets the underlying log buffer size in kilobytes

  • The date format pattern used for rendering dates in the log. The DateFormatPattern string conforms to the specification of the java.text.SimpleDateFormat class.

    Constraints

    • legal null
  • Minimum Value: 1
    Maximum Value: 100
    Default Value: 1

    Broadcasts log messages to the domain log in batch mode.

    The size of the buffer for log messages that are sent to the domain log. The buffer is maintained on the Managed Server and is broadcasted to the domain log when it is full.

    If you notice performance issues due to a high rate of log messages being generated, set this value higher. This will cause the buffer to be broadcasted less frequently from the Managed Server to the domain log. In production environments, it is not recommended to set the buffer size lower than the production default of 10.

    Constraints

    • production mode default : 10
  • Log Filter Reference
    Title: Log Filter Reference
    Contains the log filter reference.

    The filter configuration for log events being sent to the domain log.

  • Default Value: Notice
    Allowed Values: [ "Debug", "Info", "Warning", "Error", "Notice", "Critical", "Alert", "Emergency", "Off" ]

    The minimum severity of log messages going to the domain log from this server's log broadcaster. Messages with a lower severity than the specified value will not be published to the domain log.

  • Read Only: true
    Default Value: false

    Return whether the MBean was created dynamically or is persisted to config.xml

  • Minimum Value: 1
    Maximum Value: 99999
    Default Value: 7

    The maximum number of log files that the server creates when it rotates the log. This number does not include the file that the server uses to store current messages. (Requires that you enable Number of Files Limited.)

    Constraints

    • production mode default : 100
  • Minimum Value: 1
    Maximum Value: 2097150
    Default Value: 500

    The size (1 - 2097150 kilobytes) that triggers the server to move log messages to a separate file. The default is 500 kilobytes. After the log file reaches the specified minimum size, the next time the server checks the file size, it will rename the current log file as SERVER_NAME.lognnnnn and create a new one to store subsequent messages. (Requires that you specify a file rotation type of Size.)

    Constraints

    • production mode default : 5000

  • The name of the file that stores current log messages. Usually it is a computed value based on the name of the parent of this MBean. For example, for a server log, it is SERVER_NAME.log

    However, if the name of the parent cannot be obtained, the file name is weblogic.log. If you specify a relative pathname, it is interpreted as relative to the server's root directory.

    To include a time and date stamp in the file name when the log file is rotated, add java.text.SimpleDateFormat variables to the file name. Surround each variable with percentage () characters.

    For example, if the file name is defined to be myserver_%yyyy%_%MM%_%dd%_%hh%_%mm%.log, the log file will be named myserver_yyyy_mm_dd_hh_mm.log

    When the log file is rotated, the rotated file name contains the date stamp. For example, if the log file is rotated for the first time on 2 April, 2003 at 10:05 AM, the log file that contains the old messages will be named myserver_2003_04_02_10_05.log00001

    If you do not include a time and date stamp, the rotated log files are numbered in order of creation. For example, myserver.log00007

  • Minimum Value: 1
    Default Value: 24

    The interval (in hours) at which the server saves old log messages to another file. (Requires that you specify a file rotation type of TIME.)

  • Read Only: true

    Return the unique id of this MBean instance

  • Log Filter Reference
    Title: Log Filter Reference
    Contains the log filter reference.

    The filter configuration for the server log file.

    A filter configuration defines simple filtering rules to limit the volume of log messages written to the log file.

  • The directory where the rotated log files will be stored. By default the rotated files are stored in the same directory where the log file is stored.

  • Default Value: Trace
    Allowed Values: [ "Trace", "Debug", "Info", "Notice", "Warning" ]

    The minimum severity of log messages going to the server log file. By default all messages go to the log file.

  • Default Value: Info
    Allowed Values: [ "Trace", "Debug", "Info", "Notice", "Warning" ]

    The minimum severity of log messages going to all log destinations.

  • Properties
    Title: Properties
    Additional Properties Allowed: additionalProperties

    The configuration of the different logger severities keyed by name. The values are one of the predefined Severity strings namely Emergency, Alert, Critical, Error, Warning, Notice, Info, Debug, Trace.

  • Default Value: true

    Enable or disable log monitoring.

  • Minimum Value: 5
    Default Value: 30

    Timer interval in seconds to check the counts of messages logged during the interval.

  • Minimum Value: 100
    Maximum Value: 5000
    Default Value: 1000

    Maximum number of unique message signatures that will be monitored during the throttle interval.

  • Minimum Value: 10
    Maximum Value: 500
    Default Value: 50

    Cut-off length of the log message for evaluation during throttle period. The log message length is truncated to this length for evaluation of repeated logging events.

  • Minimum Value: 5
    Default Value: 1500

    The threshold number of messages logged during the evaluation period which enables or disables the throttling.

    Once throttling is enabled messages with the same repeating message signatures are throttled. Every nth repeated message specified by this attribute is logged in a monitoring cycle.

  • Read Only: true

    The user-specified name of this MBean instance.

    This name is included as one of the key properties in the MBean's javax.management.ObjectName

    Name=user-specified-name

    Constraints

    • legal null

  • Optional information that you can include to describe this configuration.

    WebLogic Server saves this note in the domain's configuration file (config.xml) as XML PCDATA. All left angle brackets (<) are converted to the xml entity <. Carriage returns/line feeds are preserved.

    Note: If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.

  • Default Value: true

    Indicates whether to limit the number of log files that this server instance creates to store old messages. (Requires that you specify a file rotation type of SIZE or TIME.)

    After the server reaches this limit, it deletes the oldest log file and creates a new log file with the latest suffix.

    If you do not enable this option, the server creates new files indefinitely and you must clean up these files as you require.

    Constraints

    • production mode default : true
  • Properties
    Title: Properties
    Additional Properties Allowed: additionalProperties

    Specifies the platform logger and the associated level names set through the WebLogic Server configuration.

    Note the following behavior:

    • The configuration is applicable for java.util.logging.Logger instances in the JDK's default global LogManager.

    • 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.

    • If your WebLogic domain includes Oracle JRF and is configured to use Oracle Diagnostic Logging (ODL), the java.util.logging levels set on the LogMBean.PlatformLoggerLevels attribute are ignored. For information about how to configure ODL logging for JDK platform loggers, see Managing Log Files and Diagnostics Data in Administering Oracle Fusion Middleware

    • As of release 14.1.2.0, one may also scope these logger criteria to a particular application context. By specifyng app-name:logger-name, instead of simply logger-name, one is saying that log messages should only appear for logger-name when operating in the context of app-name (as in, operating on a thread with the context of app-name)

  • Specifies whether the stderr of the JVM in which a WebLogic Server instance runs is redirected to the WebLogic Logging system. When this attribute is enabled, the stderr content is published to all the registered log destinations, such as the server terminal console and log file.

    Note that JVM messages are redirected asynchronously. In the event of an overload situation, these messages may be dropped. As a best practice, Oracle recommends using one of the supported logging APIs instead.

  • Specifies whether the stdout of the JVM in which a WebLogic Server instance runs is redirected to the WebLogic logging system. When this attribute is enabled, the stdout content is published to all the registered log destinations, such as the server terminal console and log file.

    Note that JVM messages are redirected asynchronously. In the event of an overload situation, these messages may be dropped. As a best practice, Oracle recommends using one of the supported logging APIs instead.

  • Default Value: true

    Specifies whether a server rotates its log file during its startup cycle. The default value in production mode is false.

    Constraints

    • production mode default : false
  • Default Value: 00:00

    Determines the start time (hour and minute) for a time-based rotation sequence.

    At the time that this value specifies, the server renames the current log file. Thereafter, the server renames the log file at an interval that you specify in File Time Span.

    Note that WebLogic Server sets a threshold size limit of 500 MB before it forces a hard rotation to prevent excessive log file growth.

    Use the following format: H:mm, where

    • is Hour in day (0-23)

    • mm is the minute in hour

  • Default Value: bySize
    Allowed Values: [ "bySize", "byTime", "none", "bySizeOrTime" ]

    Criteria for moving old log messages to a separate file.

    • NONE Messages accumulate in a single file. You must erase the contents of the file when the size is too large. Note that WebLogic Server sets a threshold size limit of 500 MB before it forces a hard rotation to prevent excessive log file growth.

    • SIZE When the log file reaches the size that you specify in FileMinSize, the server renames the file as SERVER_NAME.lognnnnn

    • TIME At each time interval that you specify in TimeSpan, the server renames the file as SERVER_NAME.lognnnnn

    After the server renames a file, subsequent messages accumulate in a new file with the name that you specified as the log file name.

  • Log Filter Reference
    Title: Log Filter Reference
    Contains the log filter reference.

    The filter configuration for log events being sent to the standard out.

  • Default Value: standard
    Allowed Values: [ "standard", "noid" ]

    The output format to use when logging to the console.

  • Default Value: true

    Specifies whether to dump stack traces to the console when included in logged message.

  • Default Value: Notice
    Allowed Values: [ "Trace", "Debug", "Info", "Warning", "Error", "Notice", "Critical", "Alert", "Emergency", "Off" ]

    The minimum severity of log messages going to the standard out. Messages with a lower severity than the specified value will not be published to standard out.

  • Items
    Title: Items

    Return all tags on this Configuration MBean

  • Minimum Value: 1
    Default Value: 5

    Defines the maximum depth of truncated stack frame after the trigger condition already met.

  • Minimum Value: 1
    Default Value: 500

    Returns the depth of stack frame that will trigger the truncation of stack frame for the remaining cascaded causes.

  • Read Only: true

    Returns the type of the MBean.

    Constraints

    • unharvestable
Nested Schema : Log Filter Reference
Type: array
Title: Log Filter Reference
Contains the log filter reference.

The filter configuration for log events being sent to the domain log.

Show Source
Nested Schema : Log Filter Reference
Type: array
Title: Log Filter Reference
Contains the log filter reference.

The filter configuration for the server log file.

A filter configuration defines simple filtering rules to limit the volume of log messages written to the log file.

Show Source
Nested Schema : Properties
Type: object
Title: Properties
Additional Properties Allowed
Show Source

The configuration of the different logger severities keyed by name. The values are one of the predefined Severity strings namely Emergency, Alert, Critical, Error, Warning, Notice, Info, Debug, Trace.

Nested Schema : Properties
Type: object
Title: Properties
Additional Properties Allowed
Show Source

Specifies the platform logger and the associated level names set through the WebLogic Server configuration.

Note the following behavior:

  • The configuration is applicable for java.util.logging.Logger instances in the JDK's default global LogManager.

  • 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.

  • If your WebLogic domain includes Oracle JRF and is configured to use Oracle Diagnostic Logging (ODL), the java.util.logging levels set on the LogMBean.PlatformLoggerLevels attribute are ignored. For information about how to configure ODL logging for JDK platform loggers, see Managing Log Files and Diagnostics Data in Administering Oracle Fusion Middleware

  • As of release 14.1.2.0, one may also scope these logger criteria to a particular application context. By specifyng app-name:logger-name, instead of simply logger-name, one is saying that log messages should only appear for logger-name when operating in the context of app-name (as in, operating on a thread with the context of app-name)

Nested Schema : Log Filter Reference
Type: array
Title: Log Filter Reference
Contains the log filter reference.

The filter configuration for log events being sent to the standard out.

Show Source
Nested Schema : Items
Type: array
Title: Items

Return all tags on this Configuration MBean

Show Source
Security
  • Type: basic
    Description: A user in the Admin security role.
Back to Top

Response

200 Response

Back to Top