Microsoft Azure Monitoring

The Message Bus Probe can be configured to obtain events from Microsoft Azure Monitoring.

The following configuration files are supplied with the probe for the integration:
  • message_bus_azure.props
  • message_bus_azure.rules
  • message_bus_azure_WebhookTransport.properties
  • message_bus_azure_config.json
To enable the Message Bus Probe to host a Webhook server for listening to incoming data from Azure Monitoring, use the following steps:
  1. Set the following properties in the message_bus_azure.props file:
    . 
    . 
    .
        SETTING PROBE LOGS, PROPS, RULES:
        MessageLog : '$OMNIHOME/log/message_bus_azure.log'
        PropsFile : '$OMNIHOME/probes//message_bus_azure.props'
        RulesFile : '$OMNIHOME/probes//message_bus_azure.rules'
    
        SETTING TRANSPORT TYPE:
        TransportType : 'Webhook'
        TransportFile : '$OMNIHOME/java/conf/message_bus_azure_WebhookTransport.properties'
    
        SETTING PARSER CONFIGURATIONS. (SUPPORTS JSON)
        TransformerFile : '$OMNIHOME/probes//message_bus_azure_parser.json'
        MessagePayload : 'JSON'
    .
    .
    .
    
  2. Set the following properties in the message_bus_azure_parser.json file:
    Note: The probe package contains a default parser configuration for Microsoft Azure Monitoring.
    
        {
        "eventSources" : [ {
        "endpoint" : "/notification",
        "name" : "NotificationAlarmParser",
        "config" : {
        "dataToRecord" : [ ],
        "messagePayload" : "json",
        "messageHeader" : "",
        "jsonNestedPayload" : "",
        "jsonNestedHeader" : "",
        "messageDepth" : 5
        }
        }, {
        "endpoint" : "/resync",
        "name" : "ResyncAlarmParser",
        "config" : {
        "dataToRecord" : [ ],
        "messagePayload" : "json",
        "messageHeader" : "",
        "jsonNestedPayload" : "",
        "jsonNestedHeader" : "",
        "messageDepth" : 3
        }
        }, {
        "name" : "OtherAlarmParser",
        "type" : "ANY",
        "config" : {
        "dataToRecord" : [ ],
        "messagePayload" : "json.data.context",
        "messageHeader" : "json",
        "jsonNestedPayload" : "",
        "jsonNestedHeader" : "",
        "messageDepth" : 5
        }
        }]
        }
    
    .
    .
    .
  3. Update webhookURI property in the message_bus_WebhookTransport.properties file.

    webhookURI=http://:<Probe's Webhook Port>/probe/webhook

    Note: webHookURI property can be initialized in one of three ways:

    Option 1: Assign host and port value in URI as described above. For example:

    webhookURI=http://:<User_Assigned_Host>:<User_Assigned_Port>/probe/webhook

    Option 2: Assign host and port value in probes properties file and assign webhookURI property with webhook path's value only. For example:

    webhookURI=/probe/webhook

    Option 3: When Host and Port are not assigned in the probe's property and transport configuration file, by default probe attempts to use hostname and port 80 to construct the webhook's path on local server. For example:

    webhookURI=http://:<Sys_Resolved_Host>:80/probe/webhook