You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a self hosted lago, but when we stream events, ( let's say more than 100 in 15s ). It doesn't show on loago dashboard in
developers events section.
Did some research on the issue,
It is an issue with postgres connection. I exposed sidekiq endpoint and checked dead messages.
The error message I saw was
ActiveRecord::ConnectionNotEstablished: connection to server at "xxx.xx.xx.xx", port 5432 failed: FATAL: remaining connection slots are reserved for roles with the SUPERUSER attribute
I will need a way to increase the number of max connection to the lago postgres db, is there any way I can do it through helm charts of lago.
The text was updated successfully, but these errors were encountered:
Deathcall404
changed the title
[BUG]: Soem events do not come to lago when there some slight increase in load
[BUG]: Soem events do not come to lago when there is slight increase in load
Sep 25, 2024
You can update the number of database connection on Lago's side by passing the DATABASE_POOL environment variable to the API and workers containers. You will have to check for the max number of connection that can be opened on Postgres side as well.
We have a self hosted lago, but when we stream events, ( let's say more than 100 in 15s ). It doesn't show on loago dashboard in
developers events section.
Did some research on the issue,
It is an issue with postgres connection. I exposed sidekiq endpoint and checked dead messages.
The error message I saw was
ActiveRecord::ConnectionNotEstablished: connection to server at "xxx.xx.xx.xx", port 5432 failed: FATAL: remaining connection slots are reserved for roles with the SUPERUSER attribute
I will need a way to increase the number of max connection to the lago postgres db, is there any way I can do it through helm charts of lago.
The text was updated successfully, but these errors were encountered: