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 FileName.n. TIME At each time interval that you specify in TimeSpan, the server renames the file as FileName.n. After the server renames a file, subsequent messages accumulate in a new file with the name that you specified in FileName.
Parsed from file BEA-WEBLOGIC-MIB.mib.txt
Company: None
Module: BEA-WEBLOGIC-MIB
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 FileName.n. TIME At each time interval that you specify in TimeSpan, the server renames the file as FileName.n. After the server renames a file, subsequent messages accumulate in a new file with the name that you specified in FileName.
Parsed from file BEA-WEBLOGIC-MIB.mib
Module: BEA-WEBLOGIC-MIB
Vendor: Independence Technologies, Inc.(ITI)
Module: BEA-WEBLOGIC-MIB
[Automatically extracted from oidview.com]
jmsSAFMessageLogFileRotationType OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "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 FileName.n. TIME At each time interval that you specify in TimeSpan, the server renames the file as FileName.n. After the server renames a file, subsequent messages accumulate in a new file with the name that you specified in FileName." ::= { jmsSAFMessageLogFileEntry 6 }
jmsSAFMessageLogFileRotationType OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current DESCRIPTION "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 FileName.n. TIME At each time interval that you specify in TimeSpan, the server renames the file as FileName.n. After the server renames a file, subsequent messages accumulate in a new file with the name that you specified in FileName." ::= { jmsSAFMessageLogFileEntry 6 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.4.1.140.625.970.1.1 | jmsSAFMessageLogFileIndex | 0 | 0 | Index column |
1.3.6.1.4.1.140.625.970.1.2 | jmsSAFMessageLogFileObjectName | 0 | 0 | ObjectName column |
1.3.6.1.4.1.140.625.970.1.3 | jmsSAFMessageLogFileType | 0 | 0 | Returns the type of the MBean. |
1.3.6.1.4.1.140.625.970.1.4 | jmsSAFMessageLogFileNumberOfFilesLimited | 0 | 0 | Indicates whether to limit the number of log files that this server instance creates to store old messages. (Requires that you … |
1.3.6.1.4.1.140.625.970.1.5 | jmsSAFMessageLogFileFileTimeSpan | 0 | 0 | The interval (in hours) at which the server saves old log messages to another file. (Requires that you specify a file rotation … |
1.3.6.1.4.1.140.625.970.1.7 | jmsSAFMessageLogFileFileCount | 0 | 0 | The maximum number of log files that the server creates when it rotates the log. This number does not include the file that the… |
1.3.6.1.4.1.140.625.970.1.8 | jmsSAFMessageLogFileFileName | 0 | 0 | None |
1.3.6.1.4.1.140.625.970.1.9 | jmsSAFMessageLogFileFileMinSize | 0 | 0 | The size (1 - 65535 kilobytes) that triggers the server to move log messages to a separate file. After the log file reaches the… |
1.3.6.1.4.1.140.625.970.1.10 | jmsSAFMessageLogFileBufferSizeKB | 0 | 0 | Gets the underlying log buffer size in kilo bytes |
1.3.6.1.4.1.140.625.970.1.11 | jmsSAFMessageLogFileDateFormatPattern | 0 | 0 | The date format pattern used for rendering dates in the log. The DateFormatPattern string conforms to the specification of the… |
1.3.6.1.4.1.140.625.970.1.12 | jmsSAFMessageLogFileRotationTime | 0 | 0 | Determines the start time (hour and minute) for a time-based rotation sequence. At the time that this value specifies, the ser… |
1.3.6.1.4.1.140.625.970.1.13 | jmsSAFMessageLogFileRotateLogOnStartup | 0 | 0 | Specifies whether a server rotates its log file during its startup cycle. |
1.3.6.1.4.1.140.625.970.1.14 | jmsSAFMessageLogFileName | 0 | 0 | The user-specified name of this MBean instance. This name is included as one of the key properties in the MBean's javax.manage… |
1.3.6.1.4.1.140.625.970.1.15 | jmsSAFMessageLogFileLogFileRotationDir | 0 | 0 | The directory where the rotated log files will be stored. By default the rotated files are stored in the same directory where t… |