code.vegaprotocol.io/vega@v0.79.0/core/docs/problem_diagnosis.md (about)

     1  There are a few tools, scripts and commands that we use to start investigating a problem while working on Vega. This document collects a few of those.
     2  
     3  # Tools worth knowing about.
     4  ## Vega specific tools
     5  * [Block explorer](https://explorer.vega.xyz/) ([repo](https://github.com/vegaprotocol/frontend-monorepo))
     6  * [`vegastream`](https://github.com/vegaprotocol/vegatools)
     7  
     8  ## API Specific tools
     9  ### GraphQL
    10  * [`GraphQURL`](https://github.com/hasura/graphqurl) is a curl like CLI tool that supports subscriptions
    11  * [`GraphQL Playground`](https://github.com/prisma-labs/graphql-playground) is served by Vega nodes serving a GraphQL API
    12  * Simplest of all: CURL can be used to post queries.
    13  
    14  ### GRPC
    15  ### REST
    16  # Some quick things
    17  
    18  ## Decoding a public key
    19  ```bash
    20  echo -n 'DrXug9ukpvwdMVAG1c2jOG+TCYVSvqCshL8dr6z+Kd8=' | base64 -d | hexdump -C | cut -b11-58 | tr -dc '[:alnum:]'
    21  ```
    22  
    23  # Some hypothetical situations
    24  
    25  <details>
    26    <summary><strong>Is [insert network] down?</strong></summary>
    27  
    28    The quickest check is [`stats.vega.trading`](https://stats.vega.trading) ([repo](https://github.com/vegaprotocol/stats/)). You should see the network there, and most or all of the stats rows should have a green block, implying it's healthy.
    29  
    30    Stats is a really simply web view of the REST [statistics endpoint](https://docs.testnet.vega.xyz/api/rest/#operation/Statistics), so you could also use curl. Choose a node serving REST from this [`devops repo document`](https://github.com/vegaprotocol/devops-infra/blob/master/doc/vega_environments.md) and then curl the statistics endpoint:
    31    ```bash
    32    curl https://n04.d.vega.xyz/statistics
    33    ```
    34  
    35    If this fails, totally it could be that the node itself is down, while the network is fine. If you get a 502 error, then the machine is up, the HTTPS proxy is working, but the Vega node is not running.
    36  
    37    If you want to skip Vega and see if Tendermint is healthy, you can try going straight to Tendermint's RPC port. Choose a node that exposes the Tendermint RPC from this [`devops` repo document](https://github.com/vegaprotocol/devops-infra/blob/master/doc/vega_environments.md) and then fetch the status endpoint:
    38    ```bash
    39    curl https://n01.d.vega.xyz/tm/status
    40    ```
    41  
    42   If those two fail, you can try `SSHing` to the machine to see what's up. The [`devops repo`](https://github.com/vegaprotocol/devops-infra/blob/master/doc/vega_environments.md) will list all of the nodes, and how you can connect to them to investigate further.
    43  </details