-
-
Notifications
You must be signed in to change notification settings - Fork 5k
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
Logrotate on error.log
#4917
Labels
area:core
issues describing changes to the core of uptime kuma
area:deployment
related to how uptime kuma can be deployed
help
question
Further information is requested
Comments
all our supported platforms already do that.
How did you install Uptime Kuma? |
error.log
You should check the error log. e.g. Print out last 100 lines:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:core
issues describing changes to the core of uptime kuma
area:deployment
related to how uptime kuma can be deployed
help
question
Further information is requested
π I have found these related issues/pull requests
x
π·οΈ Feature Request Type
Maintenance
π Feature description
I have noticed that the
error.log
becomes huge over time (here you can already see over 1 GB). Wouldn't a log rotate or automatic housekeeping make sense?βοΈ Solution
Implementing a Housekeeping
β Alternatives
No response
π Additional Context
No response
The text was updated successfully, but these errors were encountered: