Linode View

{
  "type": "object",
  "properties": {
    "alerts": {
      "type": "object",
      "properties": {
        "cpu": {
          "type": "integer",
          "description": "The percentage of CPU usage required to trigger an alert.\nIf the average CPU usage over two hours exceeds this value, we'll send you an alert.\nYour Linode's total CPU capacity is represented as 100%, multiplied by its number of\ncores.\n\nFor example, a two core Linode's CPU capacity is represented as 200%. If you want\nto be alerted at 90% of a two core Linode's CPU capacity, set the alert value to `180`.\n\nThe default value is 90% multiplied by the number of cores.\n\nIf the value is set to `0` (zero), the alert is disabled.\n"
        },
        "io": {
          "type": "integer",
          "description": "The amount of disk IO operation per second required to trigger an alert. If the average disk IO over two hours exceeds this value, we'll send you an alert. If set to `0` (zero), this alert is disabled.\n"
        },
        "network_in": {
          "type": "integer",
          "description": "The amount of incoming traffic, in Mbit/s, required to trigger an alert. If the average incoming traffic over two hours exceeds this value, we'll send you an alert. If this is set to `0` (zero), the alert is disabled.\n"
        },
        "network_out": {
          "type": "integer",
          "description": "The amount of outbound traffic, in Mbit/s, required to trigger an alert. If the average outbound traffic over two hours exceeds this value, we'll send you an alert. If this is set to `0` (zero), the alert is disabled.\n"
        },
        "transfer_quota": {
          "type": "integer",
          "description": "The percentage of network transfer that may be used before an alert is triggered. When this value is exceeded, we'll alert you. If this is set to `0` (zero), the alert is disabled.\n"
        }
      }
    },
    "backups": {
      "type": "object",
      "description": "Information about this Linode's backups status. For information about available backups, see [/linode/instances/{linodeId}/backups](/docs/api/linode-instances/#backups-list).\n",
      "properties": {
        "available": {
          "type": "boolean",
          "description": "Whether Backups for this Linode are available for restoration.\n\nBackups undergoing maintenance are not available for restoration.\n"
        },
        "enabled": {
          "type": "boolean",
          "description": "If this Linode has the Backup service enabled. To enable backups, see [POST /linode/instances/{linodeId}/backups/enable](/docs/api/linode-instances/#backups-enable).\n"
        },
        "last_successful": {
          "type": "string",
          "format": "date-time",
          "description": "The last successful backup date. 'null' if there was no previous backup."
        },
        "schedule": {
          "type": "object",
          "properties": {
            "day": {
              "type": "string",
              "description": "The day of the week that your Linode's weekly Backup is taken.\nIf not set manually, a day will be chosen for you. Backups\nare taken every day, but backups taken on this day are\npreferred when selecting backups to retain for a longer period.\n\n\nIf not set manually, then when backups are initially enabled, this\nmay come back as `Scheduling` until the `day` is automatically selected.\n",
              "enum": [
                "Scheduling",
                "Sunday",
                "Monday",
                "Tuesday",
                "Wednesday",
                "Thursday",
                "Friday",
                "Saturday"
              ]
            },
            "window": {
              "type": "string",
              "description": "The window in which your backups will be taken, in UTC. A\nbackups window is a two-hour span of time in which the backup\nmay occur.\n\n\nFor example, `W10` indicates that your backups should be\ntaken between 10:00 and 12:00. If you do not choose a backup\nwindow, one will be selected for you automatically.\n\n\nIf not set manually, when backups are initially enabled this\nmay come back as `Scheduling` until the `window` is automatically selected.\n",
              "enum": [
                "Scheduling",
                "W0",
                "W2",
                "W4",
                "W6",
                "W8",
                "W10",
                "W12",
                "W14",
                "W16",
                "W18",
                "W20",
                "W22"
              ]
            }
          }
        }
      }
    },
    "created": {
      "type": "string",
      "format": "date-time",
      "description": "When this Linode was created."
    },
    "group": {
      "type": "string",
      "description": "A deprecated property denoting a group label for this Linode.\n"
    },
    "host_uuid": {
      "type": "string",
      "format": "uuid",
      "description": "The Linode's host machine, as a UUID."
    },
    "hypervisor": {
      "type": "string",
      "description": "The virtualization software powering this Linode.\n",
      "enum": [
        "kvm"
      ]
    },
    "id": {
      "type": "integer",
      "description": "This Linode's ID which must be provided for all operations impacting this Linode.\n"
    },
    "image": {
      "type": "object"
    },
    "ipv4": {
      "type": "array",
      "description": "This Linode's IPv4 Addresses. Each Linode is assigned a single public IPv4 address\nupon creation, and may get a single private IPv4 address if needed. You may need to\n[open a support ticket](/docs/api/support/#support-ticket-open)\nto get additional IPv4 addresses.\n\nIPv4 addresses may be reassigned between your Linodes, or shared with other Linodes.\nSee the [/networking](/docs/api/networking/) endpoints for details.\n",
      "items": {
        "type": "string"
      }
    },
    "ipv6": {
      "type": "string",
      "format": "ipv6/128",
      "description": "This Linode's IPv6 SLAAC address. This address is specific to a Linode, and may not be shared. If the Linode has not been assigned an IPv6 address, the return value will be `null`.\n"
    },
    "label": {
      "type": "string",
      "description": "The Linode's label is for display purposes only. If no label is provided for a Linode,\na default will be assigned.\n\nLinode labels have the following constraints:\n\n  * Must begin and end with an alphanumeric character.\n  * May only consist of alphanumeric characters, dashes (`-`), underscores (`_`) or periods (`.`).\n  * Cannot have two dashes (`--`), underscores (`__`) or periods (`..`) in a row.\n"
    },
    "region": {
      "type": "string",
      "description": "This is the [Region](/docs/api/regions/#regions-list) where the Linode was deployed. A Linode's region can only be changed by initiating a [cross data center migration](/docs/api/linode-instances/#dc-migrationpending-host-migration-initiate).\n"
    },
    "specs": {
      "type": "object",
      "description": "Information about the resources available to this Linode.",
      "properties": {
        "disk": {
          "type": "integer",
          "description": "The amount of storage space, in MB, this Linode has access to. A typical Linode will divide this space between a primary disk with an `image` deployed to it, and a swap disk, usually 512 MB. This is the default configuration created when deploying a Linode with an `image` through [POST /linode/instances](/docs/api/linode-instances/#linode-create). While this configuration is suitable for 99% of use cases, if you need finer control over your Linode's disks, see the [/linode/instances/{linodeId}/disks](/docs/api/linode-instances/#disks-list) endpoints.\n"
        },
        "memory": {
          "type": "integer",
          "description": "The amount of RAM, in MB, this Linode has access to. Typically a Linode will choose to boot with all of its available RAM, but this can be configured in a Config profile, see the [/linode/instances/{linodeId}/configs](/docs/api/linode-instances/#configuration-profiles-list) endpoints and the LinodeConfig object for more information.\n"
        },
        "transfer": {
          "type": "integer",
          "description": "The amount of network transfer this Linode is allotted each month."
        },
        "vcpus": {
          "type": "integer",
          "description": "The number of vcpus this Linode has access to. Typically a Linode will choose to boot with all of its available vcpus, but this can be configured in a Config Profile, see the [/linode/instances/{linodeId}/configs](/docs/api/linode-instances/#configuration-profiles-list) endpoints and the LinodeConfig object for more information.\n"
        }
      }
    },
    "status": {
      "type": "string",
      "description": "A brief description of this Linode's current state. This field may change without direct action from you. For example, when a Linode goes into maintenance mode its status will display \"stopped\".\n",
      "enum": [
        "running",
        "offline",
        "booting",
        "rebooting",
        "shutting_down",
        "provisioning",
        "deleting",
        "migrating",
        "rebuilding",
        "cloning",
        "restoring",
        "stopped"
      ]
    },
    "tags": {
      "type": "array",
      "description": "An array of tags applied to this object.  Tags are for organizational purposes only.\n",
      "items": {
        "type": "string"
      }
    },
    "type": {
      "type": "string",
      "description": "This is the [Linode Type](/docs/api/linode-types/#types-list) that this Linode was deployed with.\nTo change a Linode's Type, use [POST /linode/instances/{linodeId}/resize](/docs/api/linode-instances/#linode-resize).\n"
    },
    "updated": {
      "type": "string",
      "format": "date-time",
      "description": "When this Linode was last updated."
    },
    "watchdog_enabled": {
      "type": "boolean",
      "description": "The watchdog, named Lassie, is a Shutdown Watchdog that monitors your Linode and will reboot it if it powers off unexpectedly. It works by issuing a boot job when your Linode powers off without a shutdown job being responsible.\nTo prevent a loop, Lassie will give up if there have been more than 5 boot jobs issued within 15 minutes.\n"
    }
  }
}