100 Idle connection to database (PostgreSQL)

[JohnDotOwl]

Telescope Version

5.7.0

Laravel Version

11

PHP Version

8.3

Database Driver & Version

PostgreSQL

Description

For a long time i've been wondering what is causing 100+ database connection per application. I found kinda found out that it's from Telescope , basically when it's enabled, i see 100 session, mostly idle. Not sure if it's me facing this issue but yeah it's been going on for years.

Larvel 10,11,12
PostgreSQL 15 16 17
OS : Ubuntu 22 , 23 , 24
Any idea how i can debug this issue ?

Steps To Reproduce

Enable telescope

[jaspertey]

I'm not using Postgres, but have also been troubleshooting issues with overwhelming database connections by Telescope. I did manage to capture the database process list during the most recent incident, which showed 100+ of these:

I have yet to trace exactly where in the app they are originating from (the full query isn't captured in each of the above) - but I do think it is application-related, since I don't see this happening on all apps.

[tygoegmond]

Had the same issue on MySQL.

| 11294 | user                    | 10.0.0.103:46814         | database_name    | Execute                                    |      39 | updating                                                 | update `telescope_entries` set `should_display_on_index` = 0 where `type` = 'exception' and `family_ |
| 11301 | user                    | 10.0.0.101:15792         | database_name    | Execute                                    |      10 | updating                                                 | update `telescope_entries` set `should_display_on_index` = 0 where `type` = 'exception' and `family_ |
| 11406 | user                    | 10.0.0.103:54718         | database_name    | Execute                                    |      33 | updating                                                 | update `telescope_entries` set `should_display_on_index` = 0 where `type` = 'exception' and `family_ |

This resulted in the octane server stopping continuously, and randomly slow requests.

  |   | 2025-05-12 10:52:51.159 | worker stopped, and will be restarted |  
  |   | 2025-05-12 10:52:51.149 | 200    POST /api/hub/v2/chargers/xxx/handle/metervalues ..... 74.00 ms |  
  |   | 2025-05-12 10:52:51.113 | 200    POST /api/hub/v2/chargers/xxx/handle/metervalu... 100.00 ms |  
  |   | 2025-05-12 10:52:50.975 | 400    POST /api/v2/teams/xxx/chargers/xxx/commands/cha... 48.00 ms |  
  |   | 2025-05-12 10:52:50.972 | 200    GET /api/healthcheck ........................................ 56.00 ms |  
  |   | 2025-05-12 10:52:50.934 | worker stopped |  
  |   | 2025-05-12 10:52:50.934 | 500    POST /api/hub/v2/chargers/xxx/handle/statusnotif... 34047.00 ms |  
  |   | 2025-05-12 10:52:50.934 | worker stopped, and will be restarted |  
  |   | 2025-05-12 10:52:50.900 | 404    GET /api/v2/teams/xxx/meters ........................... 20.00 ms |  
  |   | 2025-05-12 10:52:50.842 | 200    GET /api/healthcheck ........................................ 85.00 ms |  
  |   | 2025-05-12 10:52:50.785 | 200    GET /api/healthcheck ........................................ 82.00 ms |  
  |   | 2025-05-12 10:52:50.611 | 200    POST /api/hub/v2/chargers/xxx/handle/metervalues ..... 85.00 ms |  
  |   | 2025-05-12 10:52:50.514 | 200    GET /api/v3/sites/xxx/gr... 246.00 ms |  
  |   | 2025-05-12 10:52:50.437 | 200    POST /api/hub/v2/chargers/xxx/handle/statusnotifica... 24.00 ms |  
  |   | 2025-05-12 10:52:50.392 | 200    GET /api/healthcheck ........................................ 82.00 ms |  
  |   | 2025-05-12 10:52:50.308 | 200    GET /api/v2/teams/xxx/chargers/xxx ................ 43.00 ms |  
  |   | 2025-05-12 10:52:50.281 | 200    GET /api/healthcheck ........................................ 82.00 ms |  
  |   | 2025-05-12 10:52:50.222 | 200    POST /api/hub/v2/chargers/xxx/handle/me... 99.00 ms |  
  |   | 2025-05-12 10:52:50.169 | 200    POST /api/hub/v2/chargers/xxx/handle/statusnotifica... 53.00 ms |  
  |   | 2025-05-12 10:52:50.026 | 200    POST /api/hub/v2/chargers/xxx/handle/bootnotificati... 64.00 ms |  
  |   | 2025-05-12 10:52:49.964 | 200    POST /api/hub/v2/chargers/xxx/handle/metervalues ..... 70.00 ms |  
  |   | 2025-05-12 10:52:49.923 | 200    POST /api/hub/v2/chargers/xxx/handle/metervalues ..... 70.00 ms |  
  |   | 2025-05-12 10:52:49.801 | 200    GET /api/v2/teams/xxx/chargers/xxx/metervalues .... 65.00 ms |  
  |   | 2025-05-12 10:52:49.657 | 500    POST /api/hub/v2/chargers/xxx/handle/metervalues ... 30004.00 ms |  
  |   | 2025-05-12 10:52:49.657 | worker stopped |  
  |   | 2025-05-12 10:52:49.657 | worker stopped, and will be restarted |  
  |   | 2025-05-12 10:52:49.599 | 200    GET /api/v2/teams/xxx/chargers/xx/metervalues .... 64.00 ms |  
  |   | 2025-05-12 10:52:49.351 | 200    GET /api/v2/teams/xxx/chargers/xx ................ 55.00 ms |  
  |   | 2025-05-12 10:52:49.320 | 200    GET /api/v2/teams/xx/chargers/xxx/metervalues .... 49.00 ms |  
  |   | 2025-05-12 10:52:49.310 | 200    GET /api/v2/teams/xxx/chargers/xxx/metervalues .... 58.00 ms |  
  |   | 2025-05-12 10:52:49.279 | 200    POST /api/hub/v2/chargers/xxx/handle/metervalues ..... 98.00 ms |  
  |   | 2025-05-12 10:52:49.169 | 200    GET /api/v2/teams/xxx/chargers/xxx ............... 736.00 ms |  
  |   | 2025-05-12 10:52:49.147 | 200    POST /api/hub/v2/chargers/xxx/handle/metervalues .... 130.00 ms |  
  |   | 2025-05-12 10:52:49.054 | 200    GET /api/healthcheck ........................................ 80.00 ms |  
  |   | 2025-05-12 10:52:48.878 | 200    GET /api/v2/teams/xxx/chargers/xxx ................ 53.00 ms |  
  |   | 2025-05-12 10:52:48.872 | 200    POST /api/hub/v2/chargers/xxx/handle/metervalues ..... 94.00 ms |  
  |   | 2025-05-12 10:52:48.831 | 200    GET /api/v2/teams/xxx/chargers/xxx ................ 48.00 ms |  
  |   | 2025-05-12 10:52:48.826 | 200    GET /api/v2/teams/xxx/chargers/xxx/metervalues .... 73.00 ms |  
  |   | 2025-05-12 10:52:48.817 | 200    GET /api/healthcheck ........................................ 80.00 ms |  
  |   | 2025-05-12 10:52:48.759 | 200    POST /api/hub/v2/chargers/xxx/handle/metervalues ...... 80.00 ms |  
  |   | 2025-05-12 10:52:48.706 | worker stopped |  
  |   | 2025-05-12 10:52:48.706 | 500    GET /api/v3/chargers/3595aa7b-675e-4bb5-99e4-beac4c6d25... 32596.00 ms

After removing Telescope, the request latency and related issues were resolved.