large "Application Logs"

[andreas-arkulpa]

Hi @andrasbacsai,

first of all thanks for the amazing tool! I really like coolify.

We have an application which produces a large amount of application logs.
When we want to take a look at the application logs in the coolify dashboard the application crashes. If there is no parameter "since" added to the query it will load all logs sine timestamp 0.

You can see the params here: https://docs.docker.com/engine/api/v1.37/#operation/ContainerLogs

coolify/src/routes/applications/[id]/logs/index.json.ts

Line 25 in 2971e14

logs: (await container.logs({ stdout: true, stderr: true, timestamps: true }))

Can you think about adding pagination for loading the logs? Maybe it is also an idea to add the "tail" parameter to only load the last x log entries?

You can also tell me where to add the pagination so I can help you with that.

[andrasbacsai]

Pagination would be a nice addition to the logs! Thanks for the suggestion!

[andreas-arkulpa]

Thank you very much!!!

[andrasbacsai]

The next version was released. Let me know if it's better now.

There is plenty of room for improvements, but it should be better.

[andreas-arkulpa]

Thanks for your help!
It seems that this issue is not fixed, as loading all logs in the docker-host causes the application to crash (there are many large logs). I think it is also needed to add a limit in this line - the param since or tail should be added here also, if I get it right.

coolify/src/routes/applications/[id]/logs/index.json.ts

Line 25 in 2971e14

logs: (await container.logs({ stdout: true, stderr: true, timestamps: true }))

[andrasbacsai]

Ah, okay! :) For now, I will limit it to 5000. Is it okay for you?

I'm currently investigating a possible solution for logging applications into a time-series database (fluentbit + influxdb). After this feature, the logs won't be queried from the containers, but from a database (in real-time).

[andreas-arkulpa]

Thanks again for your help!
5000 sounds good - I think it should work.