# DatadogAPIClient::V1::DowntimeChild ## Properties | Name | Type | Description | Notes | | ----------------- | ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------- | | **active** | **Boolean** | If a scheduled downtime currently exists. | [optional][readonly] | | **canceled** | **Integer** | If a scheduled downtime is canceled. | [optional][readonly] | | **creator_id** | **Integer** | User ID of the downtime creator. | [optional][readonly] | | **disabled** | **Boolean** | If a downtime has been disabled. | [optional] | | **downtime_type** | **Integer** | `0` for a downtime applied on `\*` or all, `1` when the downtime is only scoped to hosts, or `2` when the downtime is scoped to anything but hosts. | [optional][readonly] | | **\_end** | **Integer** | POSIX timestamp to end the downtime. If not provided, the downtime is in effect indefinitely until you cancel it. | [optional] | | **id** | **Integer** | The downtime ID. | [optional][readonly] | | **message** | **String** | A message to include with notifications for this downtime. Email notifications can be sent to specific users by using the same `@username` notation as events. | [optional] | | **monitor_id** | **Integer** | A single monitor to which the downtime applies. If not provided, the downtime applies to all monitors. | [optional] | | **monitor_tags** | **Array<String>** | A comma-separated list of monitor tags. For example, tags that are applied directly to monitors, not tags that are used in monitor queries (which are filtered by the scope parameter), to which the downtime applies. The resulting downtime applies to monitors that match ALL provided monitor tags. For example, `service:postgres` **AND** `team:frontend`. | [optional] | | **parent_id** | **Integer** | ID of the parent Downtime. | [optional] | | **recurrence** | [**DowntimeRecurrence**](DowntimeRecurrence.md) | | [optional] | | **scope** | **Array<String>** | The scope(s) to which the downtime applies. For example, `host:app2`. Provide multiple scopes as a comma-separated list like `env:dev,env:prod`. The resulting downtime applies to sources that matches ALL provided scopes (`env:dev` **AND** `env:prod`). | [optional] | | **start** | **Integer** | POSIX timestamp to start the downtime. If not provided, the downtime starts the moment it is created. | [optional] | | **timezone** | **String** | The timezone in which to display the downtime's start and end times in Datadog applications. | [optional] | | **updater_id** | **Integer** | ID of the last user that updated the downtime. | [optional][readonly] | ## Example ```ruby require 'datadog_api_client/v1' instance = DatadogAPIClient::V1::DowntimeChild.new( active: true, canceled: 1412799983, creator_id: 123456, disabled: false, downtime_type: 2, _end: 1412793983, id: 1626, message: Message on the downtime, monitor_id: 123456, monitor_tags: ["*"], parent_id: 123, recurrence: null, scope: ["env:staging"], start: 1412792983, timezone: America/New_York, updater_id: 123456 ) ```