9932f191b5
* Troubleshoot service to service comms * adjustments * breaking fix * api-docs breaking fix * Links added to CLI pages * Update website/content/docs/troubleshoot/troubleshoot-services.mdx Co-authored-by: Eric Haberkorn <erichaberkorn@gmail.com> * Update website/content/docs/troubleshoot/troubleshoot-services.mdx Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> * Update website/content/docs/troubleshoot/troubleshoot-services.mdx Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> * nav re-ordering * Edits recommended in code review --------- Co-authored-by: Eric Haberkorn <erichaberkorn@gmail.com> Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
32 lines
1.1 KiB
Plaintext
32 lines
1.1 KiB
Plaintext
---
|
|
layout: commands
|
|
page_title: 'Commands: Troubleshoot'
|
|
description: >-
|
|
The `consul troubleshoot` command provides tools to troubleshoot Consul's service mesh configuration.
|
|
---
|
|
|
|
# Consul Troubleshooting
|
|
|
|
Command: `consul troubleshoot`
|
|
|
|
Use the `troubleshoot` command to diagnose Consul service mesh configuration or network issues. For additional information about using the `troubleshoot` command, including explanations, requirements, usage instructions, refer to the [service-to-service troubleshooting overview](/consul/docs/troubleshoot/troubleshoot-services).
|
|
|
|
## Usage
|
|
|
|
```text
|
|
Usage: consul troubleshoot <subcommand> [options]
|
|
|
|
# ...
|
|
|
|
Subcommands:
|
|
|
|
proxy Troubleshoots service mesh issues from the current Envoy instance
|
|
upstreams Gets upstream Envoy identifiers and IPs configured for the proxy
|
|
```
|
|
|
|
For more information, examples, and usage about a subcommand, click on the name
|
|
of the subcommand in the sidebar or one of the links below:
|
|
|
|
- [proxy](/consul/commands/troubleshoot/proxy)
|
|
- [upstreams](/consul/commands/troubleshoot/upstreams)
|