New http_check recipe+template

recipes/http_check.rb

@@ -0,0 +1,23 @@
+include_recipe 'datadog::dd-agent'
+
+# Build a data structure with configuration.
+# @see http://docs.datadoghq.com/guides/network_checks/
+# @example
+#   node.override['datadog']['http_check']['instances'] = [
+#     {
+#       'name' => 'MyHTTPcheck',
+#       'url' => 'http://my.server/some/service',
+#       'timeout' => '15',
+#       'content_match' => 'string to match',
+#       'include_content' => true,
+#       'collect_response_time' => true,
+#       'skip_event' => true,
+#       'tags' => [
+#        'myApp',
+#        'serviceName'
+#       ]
+#     }
+#   ]
+datadog_monitor 'http_check' do
+  instances node['datadog']['http_check']['instances']
+end

templates/default/http_check.yaml.erb

@@ -1,33 +1,5 @@
-init_config:
-
-# To notify on every service, set a list of notified uses here.
-#
-#    notify:
-#        - user1@example.com
-#        - pagerduty
-
-instances:
-#    -   name: My first service
-#        url: http://some.url.example.com
-#        timeout: 1
-
-         # If your service uses basic authentication, you can optionally
-         # specify a username and password that will be used in the check.
-#        username: user
-#        password: pass
+<%# Sanitize the compiled Mash to standard Array/Hash objects by way of JSON -%>
+<%= JSON.parse(({ 'instances' => @instances }).to_json).to_yaml %>
 
-         # The (optional) window and threshold parameters allow you to trigger
-         # alerts only if the check fails x times within the last y attempts
-         # where x is the threshold and y is the window.
-
-#        threshold: 3
-#        window: 5
-
-#    -   name: My second service
-#        url: https://another.url.example.com
-
-         # For service-specific notifications, you can optionally specify
-         # a list of users to notify within the service configuration.
-#        notify:
-#           - user2@example.com
-#           - pagerduty
+init_config:
+# Nothing to configure here