Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 12 additions & 14 deletions troubleshoot/ingest/logstash/diagnostic.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,28 +50,26 @@ To capture a {{ls}} diagnostic:

The following command options are recommended:

::::{tab-set}
:::{tab-item} Unix-based systems
* Unix-based systems

```sh
sudo ./diagnostics.sh --type logstash-local --host 127.0.0.1 --port 9600 --bypassDiagVerify
```
:::

:::{tab-item} Windows
```sh
sudo ./diagnostics.sh --type logstash-local --host 127.0.0.1 --port 9600 --bypassDiagVerify
```

* Windows

```sh
.\diagnostics.bat --type logstash-local --host 127.0.0.1 --port 9600 --bypassDiagVerify
```
```sh
.\diagnostics.bat --type logstash-local --host 127.0.0.1 --port 9600 --bypassDiagVerify
```

::::{tip}

You can run the script in three [modes](https://github.com/elastic/support-diagnostics#diagnostic-types):

* `local` (default, recommended): Polls the [{{ls}} API](https://www.elastic.co/docs/api/doc/logstash/), gathers operating system info, and captures node logs.
* `remote`: Establishes an ssh session to the applicable target server to pull the same information as `local`.
* `api`: Polls the [{{ls}} API](https://www.elastic.co/docs/api/doc/logstash/). All other data must be collected manually.

::::

3. When the script has completed, verify that no errors were logged to `diagnostic.log`. If the log file contains errors, refer to [Diagnose errors in `diagnostic.log`](#diagnostic-log-errors).
Expand Down
Loading