Add logs config to envoy

envoy/README.md

@@ -131,6 +131,24 @@ If you care only about the cluster name and grpc service, you would add this to
 
 `^cluster\.<CLUSTER_NAME>\.grpc\.<GRPC_SERVICE>\.`
 
+#### Log Collection
+
+To enable collecting logs in the Datadog Agent, update `logs_enabled` in `datadog.yaml`:
+```
+    logs_enabled: true
+```
+
+Next, edit `envoy.d/conf.yaml` by uncommenting the `logs` lines at the bottom. Update the logs `path` with the correct path to your Envoy log files.
+
+```yaml
+ logs:
+   - type: file
+     path: /var/log/envoy.log
+     source: envoy
+     service: envoy
+```
+
+
 ### Validation
 
 [Run the Agent's `status` subcommand][11] and look for `envoy` under the Checks section.

envoy/datadog_checks/envoy/data/conf.yaml.example

@@ -84,3 +84,21 @@ instances:
     # tags:
     #   - <KEY_1>:<VALUE_1>
     #   - <KEY_2>:<VALUE_2>
+
+
+## Log Section (Available for Agent >=6.0)
+##
+## type - mandatory - Type of log input source (tcp / udp / file / windows_event)
+## port / path / channel_path - mandatory - Set port if type is tcp or udp. Set path if type is file. Set channel_path if type is windows_event
+## service - mandatory - Name of the service that generated the log
+## source  - mandatory - Attribute that defines which Integration sent the logs
+## sourcecategory - optional - Multiple value attribute. Used to refine the source attribute
+## tags: - optional - Add tags to the collected logs
+##
+## Discover Datadog log collection: https://docs.datadoghq.com/logs/log_collection/
+#
+# logs:
+#   - type: file
+#     path: /var/log/envoy.log
+#     source: envoy
+#     service: envoy