Methods Changed in Call Home

Search (SHIFT+S)



Changes to Send Alert

Create an alert event with error logs attached, which aid in troubleshooting customer issues and sends it to ConnectEMC


Query Parameter Changes

sourceThe service from which this API is invoked. Allowed values: CONTROLLER, OBJECT Default: CONTROLLER
event_idEvent id for these alerts Allowed values: 999, 599 Default: 999
node_idThe ids of the nodes for which log data is collected. Allowed values: standalone,syssvc-node1,syssvc-node2 etc
node_nameThe names of the nodes for which log data is collected. Allowed values: Current values of node_x_name properties
log_nameThe names of the log files to process.
severityThe minimum severity level for a logged message. Allowed values:0-9. Default value: 7
startThe start datetime of the desired time window. Value is inclusive. Allowed values: "yyyy-MM-dd_HH:mm:ss" formatted date or datetime in ms. If not specified, it will start with the oldest messages first.
endThe end datetime of the desired time window. Value is inclusive. Allowed values: "yyyy-MM-dd_HH:mm:ss" formatted date or datetime in ms. If not specified, will continue until the latest log is retrieved, or the maxCount limit is met.
msg_regexA regular expression to which the log message conforms.
maxcountMaximum number of log messages to retrieve. This may return more than max count, if there are more messages with same timestamp as of the latest message. Value should be greater than 0.
forceAttachLogsIf true, the connectemc alert is always sent out with logs attached. If the log size exceeds the max attachment size specified in logsvc.properties, the connectemc alert will not be sent. If false, the connectemc alert is sent regardless of the log size. If the log size exceeds the max attachment size, the alert is sent out without the log attachment. By default, this parameter is false.
forceIf 1, will run multiple requests at same time.

Response Payload Changes

Field Description Type Notes
<task>
<op_id> String
<resource>    
<name> The name of the resource String
<id> ViPR ID of the related object URI
<link> A hyperlink to the related object
</resource>      
<message> String
<tenant>    
<id> ViPR ID of the related object URI
<link> A hyperlink to the related object
</tenant>      
<associated_resources> A list of links for associated resources
<associated_resource>     0-* Elements
<name> The name of the resource String
<id> ViPR ID of the related object URI
<link> A hyperlink to the related object
</associated_resource>      
</associated_resources>
<state> String
<message> The task detail message String
<description> String
<service_error>    
<code> The numerical code associated with the error encountered when processing a service request Integer
<description> The description of the error String
<details> Detailed information concerning the error String
</service_error>      
<start_time> DateTime
<end_time> DateTime
<service_error>    
<code> The numerical code associated with the error encountered when processing a service request Integer
<description> The description of the error String
<details> Detailed information concerning the error String
</service_error>      
<progress> Integer
<workflow>    
<id> ViPR ID of the related object URI
<link> A hyperlink to the related object
</workflow>      
<queuedStartTime> DateTime
<queueName> String
<name> The name assigned to this resource in ViPR. The resource name is set by a user and can be changed at any time. It is not a unique identifier. String
<id> An identifier that is generated by ViPR when the resource is created. The resource ID is guaranteed to be unique and immutable across all virtual data centers for all time. URI Valid Values:
  •  urn:storageos:resource-type:UUID:
<link> A hyperlink to the details for this resource
<creation_time> A timestamp that shows when this resource was created in ViPR DateTime Valid Values:
  •  YYYY-MM-DDTHH:mm:ssZ
<tags> Keywords and labels that can be added by a user to a resource to make it easy to find when doing a search.
<tag> String 0-* Elements
</tags>
<inactive> Whether or not the resource is inactive. When a user removes a resource, the resource is put in this state before it is removed from the ViPR database. Boolean Valid Values:
  •  true
  •  false
<global> Boolean
<remote> Boolean
<vdc>    
<id> ViPR ID of the related object URI
<link> A hyperlink to the related object
</vdc>      
<internal> Whether or not the resource is an internal resource. Boolean Valid Values:
  •  true
  •  false
</task>
Notes: