• string dsf_monitor_id — Identifier for the Monitor.
• string label — The unique label for the Monitor.

NOTE: If all fields are left at default for the HTTP, HTTPS, SMTP, or TCP protocols, the measured system will display as ‘healthy’ or ‘online’ if it returns any return code. Adding contents to the Path field will require a 200 level return code for the measured system to display as ‘healthy’ or ‘online’.

• string protocol — The protocol to monitor.
  Valid values:
  HTTP
  HTTPS
  PING
  SMTP
  TCP
• string response_count – Minimum required ‘up’ agent responses to report response pool host as ‘up’. If ‘up’ responses are less than the minimum, host is set to failover.
  Valid values: 0, 1, 2 or 3.
• string probe_interval — How often to run the monitor. Must be twice the TTL setting.
  Valid values:
  60 – Every minute
  300 – Every 5 minutes
  600 – Every 10 minutes
  900 – Every 15 minutes
• string retries — How many retries the monitor should attempt on failure before giving up.
• string active — Indicates whether or not the Monitor is active.
  Valid values:
  Y – Monitor is active.
  N – Monitor is NOT active. Default.
• hash options — Options that pertain to the Monitor.
  • string timeout — Time (in seconds) before the connection attempt times out. The default and maximum time before a timeout is 10 seconds.
  • string port — For HTTP(S)/SMTP/TCP probes, an alternate connection port. Leaving the field blank means it will monitor the default port (80 for HTTP and TCP, 443 for HTTPS, and 25 for SMTP)
  • string path — For HTTP(S) probes, a specific path to request. Designate a path other than the root to be monitored. Paths should be supplied as a relative path to the root ‘/’ directory of the website.
  • string host — For HTTP(S) probes, a value to pass in to the Host: header.
  • string header — For HTTP(S) probes, additional header fields/values to pass in, separated by the newline character (\n). See Configuring Monitor Headers for more information on using custom headers and macros in your endpoint monitoring.
  • string expected — Designate the data expected in the protocol response while monitoring the host in the pool. Maximum length: 255 bytes. Exceeding the maximum size will result in an ‘Invalid_Data’ error at run time with the message ‘Too long’. Field is case-sensitive. Exact string match required to return ‘up’ status. For HTTP(S) probes, a case sensitive sub-string to search for in the response. For SMTP probes, a string to compare the banner against. Not used for PING, or TCP protocols.
  • hash host_override – Override host data for specific endpoint addresses.
  • string address – Address of an endpoint.
  • string host – Host to use when checking that endpoint.
• array endpoints — Endpoints that are associated with the Monitor.
• string active — Indicates whether or not the endpoint is active.
• string label — A label to identify the endpoint.
• string address — The address to monitor.
• string site_prefs — An array of 3-digit codes for the locations you want monitoring the endpoints [site_pref,site_pref . . .].
  Use the site codes from this page: https://manage.dynect.net/help/agents.html. You must be logged into your Traffic Director account to view this page.

• string dsf_monitor_id — Identifier for the Monitor.
• string label — The unique label for the Monitor.
• string protocol — The protocol to monitor.
  Valid values:
  HTTP
  HTTPS
  PING
  SMTP
  TCP
• string active — Indicates whether or not the Monitor is active.
• string response_count – Minimum required ‘up’ agent responses to report response pool host as ‘up’. If ‘up’ responses are less than the minimum, host is set to failover.
  Valid values: 0, 1, 2 or 3.
• string probe_interval — How often to run the monitor.
  Valid values:
  60 – Every minute
  300 – Every 5 minutes
  600 – Every 10 minutes
  900 – Every 15 minutes
• string retries — How many retries the monitor should attempt on failure before giving up.
• hash options — Options that pertain to the Monitor.
  • string timeout — Time (in seconds) before the connection attempt times out. The default and maximum time before a timeout is 10 seconds.
  • string port — For HTTP(S)/SMTP/TCP probes, an alternate connection port.
  • string path — For HTTP(S) probes, a specific path to request.
  • string host — For HTTP(S) probes, a value to pass in to the Host: header.
  • string header — For HTTP(S) probes, additional header fields/values to pass in, separated by the newline character (\n). See Configuring Monitor Headers for more information on using custom headers and macros in your endpoint monitoring.
  • string expected — Designate the data expected in the protocol response while monitoring the host in the pool. Maximum length: 255 bytes. Exceeding the maximum size will result in an ‘Invalid_Data’ error at run time with the message ‘Too long’. Field is case-sensitive. Exact string match required to return ‘up’ status. For HTTP(S) probes, a case sensitive sub-string to search for in the response. For SMTP probes, a string to compare the banner against. Not used for PING, or TCP protocols.
  • hash host_override – Override host data for specific endpoint addresses.
  • string address – Address of an endpoint.
  • string host – Host to use when checking that endpoint.
• array endpoints — Endpoints that are associated with the Monitor.
  • string active — Indicates whether or not the endpoint is active.
  • string label — A label to identify the endpoint.
  • string address — The address to monitor.

• string dsf_monitor_id — Required. Identifier for the Monitor.
• string label — The unique label for the Monitor.

NOTE: If all fields are left at default for the HTTP, HTTPS, SMTP, or TCP protocols, the measured system will display as ‘healthy’ or ‘online’ if it returns any return code. Adding contents to the Path field will require a 200 level return code for the measured system to display as ‘healthy’ or ‘online’.

• string protocol — The protocol to monitor.
  Valid values:
  HTTP
  HTTPS
  PING
  SMTP
  TCP
• string response_count – Required. Minimum required ‘up’ agent responses to report response pool host as ‘up’. If ‘up’ responses are less than the minimum, host is set to failover.
  Valid values: 0, 1, 2 or 3.
• string probe_interval — How often to run the monitor. Must be twice the TTL setting.
  Valid values:
  60 – Every minute
  300 – Every 5 minutes
  600 – Every 10 minutes
  900 – Every 15 minutes
• string retries — How many retries the monitor should attempt on failure before giving up.
• string active — Indicates whether or not the Monitor is active.
  Valid values:
  Y – Monitor is active.
  N – Monitor is NOT active. Default.
• hash options — Options that pertain to the Monitor.
  • string timeout — Time (in seconds) before the connection attempt times out. The default and maximum time before a timeout is 10 seconds.
  • string port — For HTTP(S)/SMTP/TCP probes, an alternate connection port. Leaving the field blank means it will monitor the default port (80 for HTTP and TCP, 443 for HTTPS, and 25 for SMTP).
  • string path — For HTTP(S) probes, a specific path to request. Designate a path other than the root to be monitored. Paths should be supplied as a relative path to the root ‘/’ directory of the website.
  • string host — For HTTP(S) probes, a value to pass in to the Host: header.
  • string header — For HTTP(S) probes, additional header fields/values to pass in, separated by the newline character (\n). See Configuring Monitor Headers for more information on using custom headers and macros in your endpoint monitoring.
  • string expected — Designate the data expected in the protocol response while monitoring the host in the pool. Maximum length: 255 bytes. Exceeding the maximum size will result in an ‘Invalid_Data’ error at run time with the message ‘Too long’. Field is case-sensitive. Exact string match required to return ‘up’ status. For HTTP(S) probes, a case sensitive sub-string to search for in the response. For SMTP probes, a string to compare the banner against. Not used for PING, or TCP protocols.
  • hash host_override – Override host data for specific endpoint addresses.
  • string address – Address of an endpoint.
  • string host – Host to use when checking that endpoint.
• array endpoints — Endpoints that are associated with the Monitor.
• string active — Indicates whether or not the endpoint is active.
• string label — A label to identify the endpoint.
• string address — The address to monitor.
• string site_prefs — An array of 3-digit codes for the locations you want monitoring the endpoints [site_pref,site_pref . . .].
  Use the site codes from this page: https://manage.dynect.net/help/agents.html. You must be logged into your Traffic Director account to view this page.

• string token — Required. The session identifier.

• hash data
  • string dsf_monitor_id — Identifier for the Monitor.
  • string label — The unique label for the Monitor.
  • string protocol — The protocol to monitor.
    Valid values:
    HTTP
    HTTPS
    PING
    SMTP
    TCP
  • string active — Indicates whether or not the Monitor is active.
  • string response_count – Minimum required ‘up’ agent responses to report response pool host as ‘up’. If ‘up’ responses are less than the minimum, host is set to failover.
    Valid values: 0, 1, 2 or 3.
  • string probe_interval — How often to run the monitor.
    Valid values:
    60 – Every minute
    300 – Every 5 minutes
    600 – Every 10 minutes
    900 – Every 15 minutes
  • string retries — How many retries the monitor should attempt on failure before giving up.
  • hash options — Options that pertain to the Monitor.
    • string timeout — Time (in seconds) before the connection attempt times out. The default and maximum time before a timeout is 10 seconds.
    • string port — For HTTP(S)/SMTP/TCP probes, an alternate connection port.
    • string path — For HTTP(S) probes, a specific path to request.
    • string host — For HTTP(S) probes, a value to pass in to the Host: header.
    • string header — For HTTP(S) probes, additional header fields/values to pass in, separated by the newline character (\n). See Configuring Monitor Headers for more information on using custom headers and macros in your endpoint monitoring.
    • string expected — Designate the data expected in the protocol response while monitoring the host in the pool. Maximum length: 255 bytes. Exceeding the maximum size will result in an ‘Invalid_Data’ error at run time with the message ‘Too long’. Field is case-sensitive. Exact string match required to return ‘up’ status. For HTTP(S) probes, a case sensitive sub-string to search for in the response. For SMTP probes, a string to compare the banner against. Not used for PING, or TCP protocols.
    • hash host_override – Override host data for specific endpoint addresses.
    • string address – Address of an endpoint.
    • string host – Host to use when checking that endpoint.
  • array endpoints — Endpoints that are associated with the Monitor.
    • string active — Indicates whether or not the endpoint is active.
    • string label — A label to identify the endpoint.
    • string address — The address to monitor.

{
	'dsf_monitor_id' => '0b95k...',			# ID shortened...
	'label'          => 'My New Monitor Label',
	'response_count' => 2,
	'probe_interval' => 60,
	'retries'        => 1,
	'protocol'       => 'HTTP',
	'options' => {
		'timeout'  => 15,
		'port'     => 8080,
		'path'     => 'testpage',
		'expected' => 'running'
	},
	'token'	=> 'asdlj34ot879834cdzjklfK'
}