fluent-plugin-datadog 0.10.4 → 0.10.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 00af8da995a6929449a6b846fd3c772ba27fa0ef
-  data.tar.gz: dc262a477d7064e2aac918059beec067d4de02fb
+  metadata.gz: 64fbcf3f2a58f4ae91945601d802bfcbbe27a411
+  data.tar.gz: a80b933ca941bdcaaf15f64f0ff2d4900e7cf967
 SHA512:
-  metadata.gz: 61ed7f93e4b22ce85e80e49bfbf3f08d78e6eda151d29c071b52cb24f92085119b68b07049211b8355d369bb5994556bd0cb89a50ed14bba37818e2d1e481973
-  data.tar.gz: e8d97a7e1cdb2c0b6c749a799f8a0dd5eed7288e7d7346f3c476c96e912aa176cf3b481bed6fbc2b6c50c1d946a858ca75ecd1ffc51cff968fef32d8340b6e0b
+  metadata.gz: 97682ce0db7b87f629be382e95d9489aec3df163a014f7b74f87642d6741a01cbc5f6ee44d321ea8917023b2499bd0cd958e1dee31a2aa0f0d3502b72d023bae
+  data.tar.gz: 7ede13e8ae2b91ae16cef2ba7a0a2323acb432ecc69dab99d2d08e0a1884fe68c7fbce426fa3209deff25aaa895a21354912eef3d4141feaf86eb7efd394763a

data/README.md

@@ -19,7 +19,8 @@ If you installed the td-agent instead
 
 To match events and send them to Datadog, simply add the following code to your configuration file.
 
-TCP example
+TCP example:
+
 ```xml
 # Match events tagged with "datadog.**" and
 # send them to Datadog
@@ -33,10 +34,10 @@ TCP example
   include_tag_key true
   tag_key 'tag'
 
-  # Optional tags
-  dd_sourcecategory 'aws'
-  dd_source 'rds' 
-  dd_tags 'app:mysql,env:prod'
+  # Optional parameters
+  dd_source '<INTEGRATION_NAME>' 
+  dd_tags '<KEY1:VALU1>,<KEY2:VALUE2>'
+  dd_sourcecategory '<MY_SOURCE_CATEGORY>'
 
 </match>
 ```
@@ -78,9 +79,22 @@ As fluent-plugin-datadog is an output_buffer, you can set all output_buffer prop
 
 ### Docker and Kubernetes tags
 
-Whether you are using kubernetes, you can enrich your logs with docker and kubernetes tags using [fluent-plugin-kubernetes_metadata_filter](https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter).
-Add the following code to your configuration file to enable the filter plugin:
-```xml
+Tags in Datadog are critical to be able to jump from one part of the product to the other. Having the right metadata associated to your logs is therefore important to jump from the container view or any container metrics to the most related logs.
+
+If your logs contain any of the following attributes, it will automatically be added as Datadog tags (with the same name as on your metrics) on your logs:
+
+* kubernetes.container_image
+* kubernetes.container_name
+* kubernetes.namespace_name
+* kubernetes.pod_name
+* docker.container_id
+
+If the Datadog Agent collect them automatically, FluentD requires a plugin for this. We recommend using [fluent-plugin-kubernetes_metadata_filter](https://github.com/fabric8io/fluent-plugin-kubernetes_metadata_filter) to collect Docker and Kubernetes metadata.
+
+Configuration example:
+
+```
+# Collect metadata for logs tagged with "kubernetes.**"
 <filter kubernetes.*>
   type kubernetes_metadata
 </filter>

data/fluent-plugin-datadog.gemspec

@@ -9,7 +9,7 @@ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
 
 Gem::Specification.new do |spec|
   spec.name          = "fluent-plugin-datadog"
-  spec.version       = "0.10.4"
+  spec.version       = "0.10.5"
   spec.authors       = ["Datadog Solutions Team"]
   spec.email         = ["support@datadoghq.com"]
   spec.summary       = "Datadog output plugin for Fluent event collector"

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: fluent-plugin-datadog
 version: !ruby/object:Gem::Version
-  version: 0.10.4
+  version: 0.10.5
 platform: ruby
 authors:
 - Datadog Solutions Team
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-06-07 00:00:00.000000000 Z
+date: 2018-11-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -86,7 +86,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.6.14
+rubygems_version: 2.5.2.3
 signing_key: 
 specification_version: 4
 summary: Datadog output plugin for Fluent event collector