From 958ba94b9d9c2b9301a5218237557ba3715ffed9 Mon Sep 17 00:00:00 2001 From: Brad Thomas <42540864+bradtho@users.noreply.github.com> Date: Tue, 8 Oct 2024 09:11:50 +1100 Subject: [PATCH] Update docker-opentelemetry.md removing duplicate command from example. --- .../opentelemetry/docker-opentelemetry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/integrations/containers-orchestration/opentelemetry/docker-opentelemetry.md b/docs/integrations/containers-orchestration/opentelemetry/docker-opentelemetry.md index 2a2ce94eac..8690e7584b 100644 --- a/docs/integrations/containers-orchestration/opentelemetry/docker-opentelemetry.md +++ b/docs/integrations/containers-orchestration/opentelemetry/docker-opentelemetry.md @@ -43,7 +43,7 @@ Metrics are collected through the [Docker Stats Receiver](https://github.com/ope To collect the Docker container event logs, the following command needs to be executed on the host machine and needs to be kept running, for monitoring all the Docker container-related events. The following command also needs a JSON file path where these container events can be dumped. ``` -docker events docker events -f 'type=container' --format '{{json .}}' > & disown +docker events -f 'type=container' --format '{{json .}}' > & disown ``` Path to this JSON file will be required in the [next step](#step-2-configure-integration), where events are sent to Sumo Logic through a filelog receiver and seen as part of the **Docker - Overview** dashboard. Also, you can add additional parameters to this command to send events for specific containers. [Learn more](https://docs.docker.com/engine/reference/commandline/events/).