Important

   

Starting version 8.9.03, BMC Server Automation is renamed to TrueSight Server Automation. This space contains information about BMC Server Automation 8.9.02 and previous versions. For TrueSight Server Automation 8.9.03 and later releases, see TrueSight Server Automation 8.9.

Configuring ManagementService notification settings

A management service in BMC Server Automation collects various information from management activities that are performed on the Application Server. Using the ManagementService component in blasadmin, you can control the transfer of notifications from the management service through the following methods of delivery:

This topic has the following sections:

To configure ManagementService notification settings

  1. Start the Application Server Administration console, as described in Starting the Application Server Administration console.

  2. Use the following blasadmin commands to control notifications and the transfer of information from the management service:

    Method of deliveryObjectiveCommands
    EmailSet the severity level of email notificationsset ManagementService EmailNotificationLevel <level>

    You can choose from the following available levels (listed in descending level of severity, or ascending level of detail): OFF/FATAL/ERROR/WARN/INFO/DEBUG/FINE/FINER/FINEST
    For more information about the activities that trigger notifications, see Notification triggers.
    Specify recipients of email notificationsset ManagementService EmailRecipients <list of emails>

    Enter a comma-separated list of email addresses of recipients.

    JMXSet the port for remote access to the Application Server using JMX

    set ManagementService JMXManagementPort #

    The default port is 9838 (base port + 38).

    Set the severity level of JMX notificationsset ManagementService JmxNotificationLevel <level>

    You can choose from the following available levels (listed in descending level of severity, or ascending level of detail): OFF/FATAL/ERROR/WARN/INFO/DEBUG/FINE/FINER/FINEST
    For more information about the activities that trigger notifications, see Notification triggers.
    SNMPSet the severity level of SNMP notificationsset ManagementService SnmpNotificationLevel <level>

    You can choose from the following available levels (listed in descending level of severity, or ascending level of detail): OFF/FATAL/ERROR/WARN/INFO/DEBUG/FINE/FINER/FINEST
    For more information about the activities that trigger notifications, see Notification triggers.
    Specify recipients of SNMP notifications

    set ManagementService SnmpRecipients <list of hosts>

    Enter a comma-separated list of SNMP hosts.

  3. Restart the Application Server.

Notification triggers

The following table lists the various Application Server activities that trigger notifications. For each trigger, the delivery methods are specified, as well as the minimum logging level that has to be set for the trigger to result in a notification.

Triggers

Delivery methods

Minimum logging level

Additon/removal/update of a profile on the Application Server launcher launcher

JMX notification

FINE

Application Server starting/started/stopped

JMX notification

FINE

Diagnostic test started/stopped

JMX notification

EMAIL notification

SNMP notification

FINE for started trigger

ERROR for stopped with error trigger

WARN for stopped with warn trigger

FINE for cancelled or completed trigger

FINE is the default if the exact stopped status is unknown

Job execution started/completed

JMX notification

INFO

Error during execution of cleanup service

JMX notification

EMAIL notification

SNMP notification

ERROR

Sample notifications

Below are examples of notifications for a diagnostic test, as received through the various modes of delivery:

Examples

SNMP notification
2017-01-26 16:24:23 blapp88-1.local [192.168.52.51] 
(via UDP: [192.168.52.51]:35000->[192.168.62.118]) 
TRAP, SNMP v1, community public
SNMPv2-SMI::enterprises.12788 Enterprise Specific Trap (3000) Uptime: 0:00:00.00
SNMPv2-SMI::enterprises.12788.1.6.1 = STRING: "Diagnostic Service"    
SNMPv2-SMI::enterprises.12788.1.6.2 = INTEGER: 11  
SNMPv2-SMI::enterprises.12788.1.6.3 = STRING: "Thu Jan 26 16:12:31 EST 2017"    
SNMPv2-SMI::enterprises.12788.1.6.4 = STRING: "bladelogic.test.TestStarted"    
SNMPv2-SMI::enterprises.12788.1.6.5 = STRING: "Test started: File Manager Diagnostic Test(1)"    
SNMPv2-SMI::enterprises.12788.1.6.6 = STRING: "fine"
Email notification
Source: Diagnostic Service
Sequence Id: 6
Date: Thu Jan 26 16:27:32 EST 2017
Notification Name: bladelogic.test.TestEnded
Summary: Test ended: BlExec Job Diagnostic Test(1)

Detail:
Name: BlExec Job Diagnostic Test(1)
Result Status: COMPLETED
Start Time: Thu Jan 26 16:26:57 EST 2017
End Time: Thu Jan 26 16:27:32 EST 2017

Logs:
==============
Info: Application Server: blapp88-1.local
Info: Started at: 1/26/17 4:26 PM
Info: Ended at: 1/26/17 4:27 PM
Was this page helpful? Yes No Submitting... Thank you

Comments