To create a downtime schedule that occurs on a weekly basis, you can use one of the following XML syntax:
Syntax 1
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<downtime>
<name>Sample2</name>
<category>Other</category>
<schedule >
<type>WEEKLY</type>
<days>
<selectedDays>SUNDAY</selectedDays>
<selectedDays>MONDAY</selectedDays>
<selectedDays>TUESDAY</selectedDays>
<selectedDays>WEDNESDAY</selectedDays>
</days>
<startTimeInSecs> 57600</startTimeInSecs>
<durationInSecs> 10800</durationInSecs>
<validFrom>2012-02-02 12:00:00</validFrom>
<validTo>2012-03-10 12:00:00</validTo>
</schedule>
<instances type="CPU">
<instance>
<attribute name="CI_UID" value="c2fa6553dd16af591b128e19feec3d49"/>
</instance>
<instance>
<attribute name="CI_UID" value="b1ta83456aa13rf352h908e19teec3d49"/>
</instance>
</instances>
</downtime>
Syntax 2
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<downtime>
<name>Sample2</name>
<category>Other</category>
<schedule >
<type>WEEKLY</type>
<days>
<selectedDays>SUNDAY</selectedDays>
</days>
<startTimeInSecs> 57600</startTimeInSecs>
<durationInSecs> 10800</durationInSecs>
<validFrom>2012-02-02 12:00:00</validFrom>
<validTo>2012-03-10 12:00:00</validTo>
</schedule>
<selectedCIs>
<ci>
<id>ciid_bizsvc1</id>
</ci>
<ci>
<id>ciid_bizsvc2</id>
</ci>
</selectedCIs>
</downtime>
The following table provides a description of the tags used in the above sample.
Tag | Description |
---|---|
<name> |
Provide a name for the downtime in the tag. |
<category> |
The category assigned to the downtime. Options include:
|
<schedule> |
Define the downtime schedule in this section of the XML. |
<type> |
Define the type of downtime schedule that you want to create. The values can be ONCE, WEEKLY, or MONTHLY. |
<days> |
Specify the days of the week when downtime for the CI type is planned for in this section. |
<startTimeInSecs> |
Specify the starting time of the scheduled downtime in seconds. For example, 57600 seconds equals to 16:00, which means that the downtime is scheduled to start at 4 P.M. on each day that is defined in the <days> tag. |
<durationInSecs> |
Specify the duration of the downtime in seconds. For example, 10800 seconds equals to 3 hours, which means that the downtime period lasts for 3 hours from 4 P.M. to 7 P.M. |
<validFrom> |
Specify the starting date and time when SHR must start collecting the downtime information for data enrichment. The date format is yyyy-mm-dd hh:mm:ss. |
<validTo> |
Specify the ending date and time when SHR must stop collecting the downtime information for data enrichment. The date format is yyyy-mm-dd hh:mm:ss. |
<instances type> |
In this section, you define the CI type that will be affected by downtime such as node, CPU, Disk, Web server, application, event, and so on. The downtime XML that you create is applicable for one CI type only. For additional CIs, you must create additional XML files. |
<instance> |
Each instance of the CI type must be defined in a separate <instance> tag. The attribute name refers to the instance metric and the value refers to the value of that metric. If a particular CI instance is defined by more than one metric, additional instances must also be defined by the same number and type of metrics. For the CI parameters, see the Model Automation XSD. |
<selectedCIs> |
In this section, you can directly define multiple CIs that will be affected by downtime. You can refer to these CIs by using their unique IDs. This section is applicable if SHR is deployed in the SaOB and APM deployment scenarios where RTSM is the topology source. |