Use the disable operation to disable Log Rotation service on sites.

Request Packet Structure

A request XML packet disabling Log Rotation service includes the disable operation node:

<packet version="1.5.0.0">
<log-rotation>
   <disable>
   ...
   </disable>
</log-rotation>
</packet>

The disable node is presented by type LogRotationDisableInput (logrotation.xsd), and its graphical representation is as follows:

• The filter node is required. Specifies the filtering rule. For more information, refer to the Available Filters section. Data type: logRotationFilterType (logrotation.xsd) .

Remarks

You can use different filtering rules in a single packet. Add as many disable operations as the number of different filtering rules.

<packet version="1.5.0.0">
<log-rotation>
   <disable>
   ...
   </disable>
...
   <disable>
   ...
   </disable>
</log-rotation>
</packet>

Response Packet Structure

The disable node of the output XML packet is presented by type LogRotationDisableOutput (logrotation.xsd) and structured as follows:

• The result node is required. It wraps the response retrieved from the server. Data type: resultFilterType (common.xsd).
• The status node is required. It specifies the execution status of the disable operation. Data type: string. Allowed values: ok | error.
• The errcode node is optional. It returns the error code if the disable operation fails. Data type: unsignedInt.
• The errtext node is optional. It returns the error message if the disable operation fails. Data type: string.
• The filter-id node is required. It returns a filtering rule parameter. For more information, refer to the Available Filters section. Data type: anySimple.
• The id node is optional. If the disable operation succeeds, it holds the ID of the site matched by the filtering rule. Data type: integer.

Samples

Disabling Log Rotation service on a single site

The following request packet disables Log Rotation service on site example.com:

<packet>
  <log-rotation>
    <disable>
        <filter>
        <site-name>example.com</site-name>
        </filter>
    </disable>
  </log-rotation>
</packet>

Response:

<packet>
  <log-rotation>
    <disable>
      <result>
        <status>ok</status>
        <filter-id>example.com</filter-id>
        <id>33</id>
      </result>
    </disable>
  </log-rotation>
</packet>

If the site was not found, the response from the server looks as follows:

<packet>
  <log-rotation>
    <disable>
      <result>
        <status>error</status>
        <errcode>1013</errcode>
        <errtext>site does not exist</errtext>
        <filter-id>example.com</filter-id>
      </result>
    </disable>
  </log-rotation>
</packet>

Disabling Log Rotation service on multiple sites

The following request packet disables Log Rotation service on sites used by the customers with ID 5 and ID 8:

<packet>
  <log-rotation>
    <disable>
        <filter>
          <owner-id>5</owner-id>
          <owner-id>8</owner-id>
        </filter>
    </disable>
  </log-rotation>
</packet>

Response (if the customer with ID 5 was not found on the server and the customer with ID 8 runs two sites (ID 17 and 29)):

<packet>
   <disable>
  <log-rotation>
      <result>
        <status>error</status>
        <errcode>1015</errcode>
        <errtext>client does not exist</errtext>
        <filter-id>5</filter-id>
      </result>
    </disable>
    <disable>
      <result>
        <status>ok</status>
        <filter-id>8</filter-id>
        <id>17</id>
      </result>
    </disable>
    <disable>
      <result>
        <status>ok</status>
        <filter-id>8</filter-id>
        <id>29</id>
      </result>
    </disable>
  </log-rotation>
</packet>