updateAlertRemote Operation

Using updateAlertRemote operation you can update existing alerts on a managed TIBCO LogLogic Appliance from a Management Station.

When using updateAlertRemote, you must specify:

Request Parameters

authToken, applianceIP, alertTypeName, name, desc, priorityName, enabled, deviceNames, usernames, trapIds, resetTime, trackIndividualDevice, alertRules, snmpOId, changeNameTo

Response

alertResponse (see alertResponse Type)

Note: The Alert-Specific Request parameters specified in the alertRules parameter are also returned. The response depends on the alert type used.

Example

SOAP request for updateAlertRemote Operation. To update a VPN Connection Alert named MyAlertName to be named NewAlertName with the priority set at high, on remote Appliance 1.2.20.100: 

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:aler="AlertService">
   <soapenv:Header/>
   <soapenv:Body>
      <aler:updateAlert>
         <aler:authToken>admin+1Y2O2W261O1C1J1X294</aler:authToken>
         <aler:applianceIP>1.2.20.100</aler:applianceIP>
         <aler:alertTypeName>VPN Connection Alert</aler:alertTypeName>
         <aler:name>MyAlertName</aler:name>
         <aler:desc>VPN Connection Alert Description</aler:desc>
         <aler:priorityName>low</aler:priorityName>
         <aler:enabled>yes</aler:enabled>
         <aler:deviceNames>10.1.2.3_04</aler:deviceNames>
         <aler:usernames>admin</aler:usernames>
         <aler:trapIds></aler:trapIds>
         <aler:resetTime>400</aler:resetTime>
         <aler:trackIndividualDevice>yes</aler:trackIndividualDevice>
         <aler:alertRules>VPNUser/LogLogicUser//VPNGroup/LogLogicGroup//disconnectReason/is denied access</aler:alertRules>
         <aler:snmpOId></aler:snmpOId>
         <aler:changeNameTo>NewAlertName</aler:changeNameTo>
      </aler:updateAlert>
   </soapenv:Body>
</soapenv:Envelope>

SOAP response for updateAlertRemote Operation: 

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Header/>
   <soapenv:Body>
      <ns:updateAlertRemoteResponse xmlns:ns="AlertService">
         <ns:return xsi:type="ax27:AlertResponse" xmlns:ax27="http://alert.services.logapp.loglogic.com/xsd" xmlns:ax28="http://services.logapp.loglogic.com/xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ax28:authToken xsi:nil="true"/>
            <ax28:resultCount>1</ax28:resultCount>
            <ax28:statusCode>2000</ax28:statusCode>
            <ax28:statusMessage>Successful</ax28:statusMessage>
            <ax28:summaryOnly>false</ax28:summaryOnly>
            <ax27:resultSet xsi:type="ax27:AlertDetail">
               <ax27:alertRules xsi:nil="true"/>
               <ax27:alertType xsi:nil="true"/>
               <ax27:desc xsi:nil="true"/>
               <ax27:devices xsi:nil="true"/>
               <ax27:enabled xsi:nil="true"/>
               <ax27:name xsi:nil="true"/>
               <ax27:networkMonitorPolicyRules xsi:nil="true"/>
               <ax27:priority xsi:nil="true"/>
               <ax27:resetTime xsi:nil="true"/>
               <ax27:snmpOId xsi:nil="true"/>
               <ax27:trackIndividualDevice xsi:nil="true"/>
               <ax27:traps xsi:nil="true"/>
               <ax27:users xsi:nil="true"/>
            </ax27:resultSet>
         </ns:return>
      </ns:updateAlertRemoteResponse>
   </soapenv:Body>
</soapenv:Envelope>