# The UI is not displaying any metrics for my new instance.

If the agent installation and PostgreSQL instance configuration have been successfully completed but are not appearing in the user interface, you can troubleshoot the issue by following these steps to identify the root cause:

## Agent Local Machine

### Agent Status

> Verify Agent Status and Upload Server Configuration

```bash
datasentinel status agent
```

```
      Agent
         Version : 1.9.3
            Port : 8282
      Start time : 2020-02-07 13:08:08
 Collection rate : high

      Proxy
            host :
            port : 0
            user :
        password :

     Upload
            host : 51.15.236.159
            port : 443

Connections
        declared : 1
         running : 1
     not running : 0
```

### Check Token

> Ensure the token is not expired

```bash
datasentinel show token
```

```
          Token : eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJleHAiOjE1ODM2OTUyNzcsImlhdCI6MTU3NjM1MTI3MiwiZGF0YWJhc2UiOiJkcy1kYXRhIn0.UQRxutKrJv7WVAaHCN3Fh_wnXJLst54s93lADIP_n-Y

   Organization : ds-data
Expiration Date : 2020-03-08 19:21:17
```

### Connection Status

> Check that the conection is `enabled` and `running` 

```bash
datasentinel show connections
```

```
name                 status     state      host                 port   user
--------------------------------------------------------------------------------
:9342                enabled    running    pg-sales-1734          9342 datasentinel
tags : application=sales,environment=production,provider=amazon,datacenter=lyon
```

### Check Agent Log File

> The agent writes all its actions in the file **`datasentinel.log`** located in the subdirectory **`log`**

{% hint style="danger" %}
No **ERROR** indications should be present.
{% endhint %}

```
2019-12-15 15:54:13,021 - datasentinel - INFO - Agent metrics sent to https://51.158.110.62:443
2019-12-15 15:54:13,041 - datasentinel - INFO - pg_store_plans size : 20
2019-12-15 15:54:13,042 - datasentinel - INFO - Interval stats cache size : 173
2019-12-15 15:54:13,110 - datasentinel - INFO - PG Server metrics sent to https://51.158.110.62:443
2019-12-15 15:54:19,742 - datasentinel - INFO - Active sessions metrics sent to https://51.158.110.62:443
2019-12-15 15:54:19,810 - datasentinel - INFO - PG status metrics sent to https://51.158.110.62:443
2019-12-15 15:54:29,823 - datasentinel - INFO - Active sessions metrics sent to https://51.158.110.62:443
2019-12-15 15:54:29,893 - datasentinel - INFO - PG status metrics sent to https://51.158.110.62:443
2019-12-15 15:54:39,879 - datasentinel - INFO - Active sessions metrics sent to https://51.158.110.62:443
2019-12-15 15:54:39,965 - datasentinel - INFO - PG status metrics sent to https://51.158.110.62:443
2019-12-15 15:54:49,980 - datasentinel - INFO - Active sessions metrics sent to https://51.158.110.62:443
2019-12-15 15:54:50,073 - datasentinel - INFO - PG status metrics sent to https://51.158.110.62:443
2019-12-15 15:55:00,075 - datasentinel - INFO - Active sessions metrics sent to https://51.158.110.62:443
2019-12-15 15:55:00,201 - datasentinel - INFO - PG status metrics sent to https://51.158.110.62:443
2019-12-15 15:55:09,209 - datasentinel - INFO - Active sessions metrics sent to https://51.158.110.62:443
2019-12-15 15:55:09,285 - datasentinel - INFO - PG status metrics sent to https://51.158.110.62:443
```

## Platform Machine

### Check Log Files

> All log files are located in the directory **`/datasentinel/log`**

Check that the file **`backend_to_influx.log`** is empty or does not contain errors