riemann.rb in logstash-output-riemann-0.1.1

- old
+ new

@@ -10,13 +10,13 @@
 # Riemann is used in Logstash much like statsd or other metric-related
 # outputs
 #
 # You can learn about Riemann here:
 #
-# * <http://riemann.io/>
+# * http://riemann.io/
 # You can see the author talk about it here:
-# * <http://vimeo.com/38377415>
+# * http://vimeo.com/38377415
 #
 class LogStash::Outputs::Riemann < LogStash::Outputs::Base
   config_name "riemann"
   milestone 1
 
@@ -39,22 +39,22 @@
   # This sets the `host` value
   # in the Riemann event
   config :sender, :validate => :string, :default => "%{host}"
 
   # A Hash to set Riemann event fields
-  # (<http://riemann.io/concepts.html>).
+  # (http://riemann.io/concepts.html).
   #
   # The following event fields are supported:
   # `description`, `state`, `metric`, `ttl`, `service`
   #
   # Tags found on the Logstash event will automatically be added to the
   # Riemann event.
   #
   # Any other field set here will be passed to Riemann as an event attribute.
   #
   # Example:
-  #
+  # [source,ruby]
   #     riemann {
   #         riemann_event => {
   #             "metric"  => "%{metric}"
   #             "service" => "%{service}"
   #         }
@@ -70,19 +70,21 @@
   # If set to true automatically map all logstash defined fields to riemann event fields.
   # All nested logstash fields will be mapped to riemann fields containing all parent keys
   # separated by dots and the deepest value.
   #
   # As an example, the logstash event:
+  # [source,ruby]
   #    {
   #      "@timestamp":"2013-12-10T14:36:26.151+0000",
   #      "@version": 1,
   #      "message":"log message",
   #      "host": "host.domain.com",
   #      "nested_field": {
   #                        "key": "value"
   #                      }
   #    }
   # Is mapped to this riemann event:
+  # [source,ruby]
   #   {
   #     :time 1386686186,
   #     :host host.domain.com,
   #     :message log message,
   #     :nested_field.key value