Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All
     

    Related Documentation

     

    Configuring JBoss and OpenNMS Logs in Junos Space

    Junos Space Network Management Platform enables you to configure log levels for JBoss and OpenNMS logs in Junos Space from the Administration workspace in the Junos Space Platform UI. You can configure log levels for the JBoss and OpenNMS logs by using the Log Configuration page of the Space Troubleshooting task group.

    You must be assigned the System Administrator role to configure logs from the Log Configuration page.

    To configure the JBoss and OpenNMS logs from the Junos Space Platform UI:

    1. On the Junos Space Platform UI, select Administration > Space Troubleshooting > Log Configuration.

      The Log Configuration page is displayed.

    2. Perform one of the following actions to configure the JBoss or OpenNMS logs, respectively:
      • Click the JBoss Logs tab.

        The log handlers configured in JBoss are listed on the page. The corresponding log filenames and log levels are also displayed in a tabular format. The Log Level column displays the existing log level for each log.

      • Click the OpenNMS Logs tab.

        The log handlers configured in OpenNMS are listed on the page. The corresponding log filenames and log levels are also displayed in a tabular format. The Log Level column displays the existing log level for each log.

      For more information about log files in Junos Space Platform, see Junos Space Network Management Platform Log Files Overview.

    3. Click the Log Level field of the log file for which you want to configure the log level.
    4. Click the down arrow to select the log level from the list.

      When you select a particular log level, the selected severity and all higher-severity log messages are recorded. For example, if you select DEBUG as the log level, log messages of severity debug, info, warn, and fatal are recorded in the log file for which you configured the log level. If you select ALL, all log messages are recorded in the log file. See Table 1 for more information about the log levels that you can select.

    5. Click Update to save the change.

      Repeat Step 2 through Step 5 to modify log levels for other JBoss and OpenNMS logs listed on the page.

    6. (Optional) Select or clear the check box in the Enable/Disable column to enable or disable logging for the corresponding log file. By default, logging for all JBoss and OpenNMS log files is enabled, unless it is disabled from the Junos Space CLI, and the default log level is WARN,

      If you select the check box, logging is enabled and the log level is set at the WARN level.

    7. Click Save to save all changes after you finish specifying the log levels.

    An audit log entry is added when you modify the log level of any log file.

    Table 1 lists the various log levels that can be configured for JBoss and OpenNMS logs.

    Table 1: Log Levels and their Descriptions

    Log Level

    Description

    OFF

    Logging is turned off.

    FATAL

    Log messages that indicate a critical service failure are recorded.

    ERROR

    Log messages that indicate a disruption in a request or the ability to service a request and all higher-severity log messages are recorded.

    WARN

    Log messages that indicate a noncritical service error and all higher-severity log messages are recorded.

    INFO

    Log messages that indicate service life-cycle events and provide other related crucial information, and all higher-severity log messages are recorded.

    DEBUG

    Log messages that convey extra information regarding life-cycle events and all higher-severity log messages are recorded.

    TRACE

    Log messages that are directly associated with any activity that corresponds to requests and all higher-severity log messages are recorded.

    ALL

    Log messages of all severity levels are recorded.

     

    Related Documentation

     

    Modified: 2016-11-18