Add some basics about troubleshooting the Collector (open-telemetry#3033

) * Add some basics about troubleshooting the Collector Added some helpful lines for troubleshooting the collector... * Add some basics about troubleshooting the Collector Add some basics about troubleshooting the Collector: To see logs for the Collector: On a Linux systemd system, logs can be found using `journalctl`: `journalctl | grep otelcol` or to find only errors: `journalctl | grep otelcol | grep Error` Co-authored-by: Bogdan Drutu <[email protected]>
dashpole · Jun 14, 2021 · 7cfbe12 · 7cfbe12
1 parent ae6e3f7
commit 7cfbe12
Showing 1 changed file with 9 additions and 1 deletion.
diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
@@ -194,6 +194,14 @@ Collector as it runs. This is an advanced use-case that should not be needed in
 
 ## Common Issues
 
+To see logs for the Collector:
+
+On a Linux systemd system, logs can be found using `journalctl`:  
+`journalctl | grep otelcol`
+
+or to find only errors:  
+`journalctl | grep otelcol | grep Error`
+
 ### Collector exit/restart
 
 The Collector may exit/restart because:
@@ -265,4 +273,4 @@ The process may fail to start in a Windows Docker container with the following
 error: `The service process could not connect to the service controller`. In
 this case the `NO_WINDOWS_SERVICE=1` environment variable should be set to force
 the collector to be started as if it were running in an interactive terminal,
-without attempting to run as a Windows service.
+without attempting to run as a Windows service.