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 [,singlematch]

    where

    singlematch—[!] ( <category> | ([<category>]/[<severity>] | [<minimumSeverity>]-[<maximumSeverity>] ))

    • !—Do not log matching events
    • <category>—SRC 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 1 shows common severity levels that you can specify by name.

      Table 1: Named Severity Levels

      Name

      Severity Level

      logmin

      1

      debug

      10

      info

      20

      notice

      30

      warning

      40

      error

      50

      crit

      60

      alert

      70

      emerg

      80

      panic

      90

      logmax

      127

      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:

      • Specify an explicit severity. For example:

        warning—Defines only warning messages

      • Specify a minimum severity and a maximum severity. For example:

        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

      • Specify no severity to log all event messages.
  • Default—No value
  • Example—Table 2 shows some examples of filters.

    Table 2: Examples of Filters for Event Messages

    Syntax

    Event Messages Saved

    /

    All event messages

    /info-

    Event messages of level info and above from all categories

    vta/debug

    Debug events from the VTA category only

    !vta,/debug

    All debug events except those from the VTA category

    !VtaMsg/info-,vtaMsg,vta

    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:

    <pathname>/<filename.log>

  • Guidelines—Make sure you have write access to the folder.
  • Default—By default, SRC 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 SRC 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