Logging Event Messages for the VTA
The VTA generates event messages that you can save in logs—either by writing the messages to text files or by using the system log (syslog) facilities.
To access the logging configuration:
- In the VTA Configuration Manager navigation pane, select Edit.
- Under Current Configuration, select Logging.
The current File and Syslog configurations appear.
Logging Events Messages to a Text File
To set up the VTA to save event messages in text files:
- In the VTA Configuration Manager navigation pane, select Edit.
- Under Current Configuration, select Logging.
- In the File section, select a file logging configuration to modify, or type a new file name in the New File box, and click Create.
The current file logging configuration appears.
See File Logging Fields.
See Saving VTA Configurations to a Directory or Local File.
File Logging Fields
In VTA Configuration Manager, you can modify the following fields in the File section of the Logging screen.
Filter
- Filter that determines the type of messages that this log file contains.
- Value—Expression. The software filters events by evaluating each subexpression from left to right. When the software finds a match, it logs or ignores the message accordingly. You can specify an unlimited number of subexpressions. The order in which you specify the subexpressions affects the result. Expressions have the format:
singlematch—[!] ( <category> | ([<category>]/[<severity>] | [<minimumSeverity>]-[<maximumSeverity>] ))
- !—Do not log matching events
- <category>—SDX component that generated the event message. To log only events in a specific category, you can define the category, which is a text string that matches the name of a category. The text string is not case sensitive. For the names of categories, view a log file for a default filter. Juniper Networks Technical Assistance Center (JTAC) can also provide category names.
- [<severity>] | [<minimumSeverity>]-[<maximumSeverity>] —Name or number in the range 1-127. A higher number indicates a higher severity level. Table 37 shows common severity levels that you can specify by name.
Enabling debug log messages has a negative affect on system performance. Do not enable debug log messages unless JTAC instructs you to do so.
You can define a severity level as follows:
warning—Defines only warning messages
info-warning—Defines messages of minimum severity level of info and a maximum severity level of warning
- Accept the default minimum (logmin) or maximum (logmax) severity by omitting the minimum or maximum severity. For example:
info-—Defines messages of minimum severity level info and maximum severity level logmax
-warning—Defines messages of minimum severity level logmin and maximum severity level warning
- Default—No value
- Example—Table 38 shows some examples of filters.
All messages from the VTA category, except those from VtaMsg category with level less than info |
Filename
- Filename that contains the current logs.
- Value—Path and filename of the current log file in the format:
- Guidelines—Make sure you have write access to the folder.
- Default—By default, SDX components and applications write log files in the folder where the application is started. If you are using the version of JBoss packaged with the SDX software, the pathname is /opt/UMC/jboss/server/default/log/.
- Example—/opt/UMC/jboss/server/default/log/vta_debug.log
Maximum File Size
- Disables or enables and sets the maximum size of the log file and the rollover file.
- Value—Number of kilobytes in the range 0-4294967295
- Guidelines—Do not set the maximum file size to a value greater than the available disk space.
- Default—1000000
Rollover Filename
- Path and filename of the rollover log file. When the log file reaches the maximum size, the software closes the log file and renames it with the name you specify for the rollover file. If a previous rollover file exists, the software overwrites it. The software then reopens the log file and continues to save event messages in it.
- Value—Path and filename of the rollover log file in the format
<pathname>/<filename.alt> - Default—No value
- Example—vta_debug.alt
Logging Events Messages to a System Logging Server
To configure the VTA to save event messages on a system logging server:
- In the VTA Configuration Manager navigation pane, select Edit.
- Under Current Configuration, select Logging.
The current logging configuration appears.
- To add a system log configuration, enter a name for the configuration in the New Syslog box, and click Create.
The Syslog configuration screen appears.
See Saving VTA Configurations to a Directory or Local File.
System Logging Fields
In VTA Configuration Manager, you can edit the following fields in the syslog section of the Logging screen.
Filter
- Filter that determines the type of messages that this log file contains.
- Value—Expression. The software filters events by evaluating each subexpression from left to right. When the software finds a match, it logs or ignores the message accordingly. You can specify an unlimited number of subexpressions. The order in which you specify the subexpressions affects the result. Expressions have the format:
singlematch—[!] ( <category> | ([<category>]/[<severity>] | [<minimumSeverity>]-[<maximumSeverity>] ))
- !—Do not log matching events
- <category>—SDX component that generated the event message. To log only events in a specific category, you can define the category, which is a text string that matches the name of a category. The text string is not case sensitive. For the names of categories, view a log file for a default filter. Juniper Networks Technical Assistance Center (JTAC) can also provide category names.
- [<severity>] | [<minimumSeverity>]-[<maximumSeverity>] —Name or number in the range 1-127. A higher number indicates a higher severity level. Table 39 shows common severity levels that you can specify by name.
Enabling debug log messages has a negative affect on system performance. Do not enable debug log messages unless JTAC instructs you to do so.
You can define a severity level as follows:
warning—Defines only warning messages
info-warning—Defines messages of minimum severity level of info and a maximum severity level of warning
- Accept the default minimum (logmin) or maximum (logmax) severity by omitting the minimum or maximum severity. For example:
info-—Defines messages of minimum severity level info and maximum severity level logmax
-warning—Defines messages of minimum severity level logmin and maximum severity level warning
- Guidelines—This field is mandatory.
- Default—No value
- Example—Table 40 shows some examples of filters.
All messages from the VTA category, except those from VtaMsg category with level less than info |
Syslog Host
- IP address or name of a host that collects event messages with a standard system logging daemon.
- Value—IP address or text string
- Default—No value