Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG]: Soem events do not come to lago when there is slight increase in load #411

Open
Deathcall404 opened this issue Sep 25, 2024 · 1 comment

Comments

@Deathcall404
Copy link

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.

Screenshot 2024-09-25 at 12 33 20 PM
@Deathcall404 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
@vincent-pochet
Copy link
Contributor

Hello @Deathcall404,

Thank you for reporting this.

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.

DATABASE_POOL appears to be missing in the documentation (https://doc.getlago.com/guide/self-hosted/docker), we will update it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants