Skip to content

Commit 314af8b

Browse files
NilsKaylyn
andauthored
Apply suggestions from code review
Took the liberty to apply the suggestions Co-Authored-By: Kaylyn <kaylyn.sigler@datadoghq.com>
1 parent f4808cd commit 314af8b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

content/en/logs/guide/docker-logs-collection-troubleshooting-guide.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,13 +3,13 @@ title: Docker Log Collection Troubleshooting Guide
33
kind: documentation
44
---
55

6-
There are a number of common issues that can get in the way when sending new container logs to Datadog via the Container Agent or a locally installed Host Agent. If you experience issues sending new logs to Datadog, this list helps you troubleshoot. If you continue to have trouble, [ email us ][1] for further assistance.
6+
There are a number of common issues that can get in the way when sending new container logs to Datadog with the Container Agent or with a locally installed Host Agent. If you experience issues sending new logs to Datadog, this list helps you troubleshoot. If you continue to have trouble, [contact our support team][1] for further assistance.
77

88
## Logging isn't enabled
99
{{< tabs >}} {{% tab "Container Installation" %}}
10-
Check if log collection has been enabled `DD_LOGS_ENABLED=true`.
10+
Check if the log collection is enabled `DD_LOGS_ENABLED=true`.
1111
{{% /tab %}} {{% tab "Host Installation" %}}
12-
Check if log collection has been enabled with `logs_enabled: true` in the `datadog.yaml` file.
12+
Check if the log collection is enabled `logs_enabled: true` in the `datadog.yaml` file.
1313
{{% /tab %}} {{< /tabs >}}
1414
## Unable to connect to Docker socket
1515

@@ -30,7 +30,7 @@ Logs Agent
3030

3131
{{< tabs >}} {{% tab "Container Installation" %}}
3232

33-
For the Container Agent, connection to the socket is handled by mounting the docker socket directly into the container. If this step hasn't been performed, you will see the following logs when the Agent starts:
33+
For the Container Agent, the connection to the socket is handled by mounting the docker socket directly into the container. If this step hasn't been performed, you see the following logs when the Agent starts:
3434

3535
```
3636
2019-10-09 14:10:58 UTC | CORE | INFO | (pkg/logs/input/container/launcher.go:51 in NewLauncher) | Could not setup the docker launcher: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

0 commit comments

Comments
 (0)