Tomcat logging and geoserver monitoring/audit questions #624
-
Hi, we've been using your geoserver image for a long time, thank you for your work on this! I've recently put the newer 2.24.0 release into our production environment and am noticing some issues (for us) with the way tomcat logging is configured, as well as with the audit/monitor functionality of geoserver. We are generating >1GB/day of tomcat localhost_access* logs, the default logger is set to hold 90 days worth. I don't see a way to manage this configuration as part of the kartoza image, is there an option I'm missing? I had an idea to add Also, we had a production outage due to geoserver taking a very long time to start, it turns out the audit functionality had generated tens of thousands of audit log files, and as part of the startup it deletes everything in the $DATADIR/monitoring/monitor_* log directory. I think the default monitoring.properties file configuration isn't ideal for production use, and my changes to the file get overwritten when the geoserver pod restarts. It looks like if I deliver my own monitor.properties file in /settings I can control the behavior, but am curious why the default is set this way, with rolling the file every 40 requests? FInally, unless I'm mistaken, it appears that the geoserver logging will get reset on start every time, unless I specify an (undocumented) env variable Thanks again, and I look forward to your thoughts on these items. |
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 5 replies
-
A couple of answers here
The startup options can also be set but I am not sure what options you will need to add there.
If you think the answers above will help you can proceed to do a PR |
Beta Was this translation helpful? Give feedback.
-
@alexkuretz Please see 3c01ba1 that resolves the majority of your issues |
Beta Was this translation helpful? Give feedback.
-
Thanks for that, I was about half-way there with a PR but hadn't finished up yet. The only immediate suggestion I'd have is to default to audit disabled, as that is the default in Geoserver. I'll give this a more thorough look and try it out.
|
Beta Was this translation helpful? Give feedback.
-
Also, in the PR I was working on I was adding these new options to the .env file so they'd be exposed to users, so far I'd added this at line 84:
I'm happy to continue working on my PR if that would be helpful, do you prefer I make comment suggestions to your PR or just submit my own in the next day or two? |
Beta Was this translation helpful? Give feedback.
-
I've submitted the PR and look forward to your feedback. #627 |
Beta Was this translation helpful? Give feedback.
-
We had another production outage this week when the server paused for a long time deleting 200k+ audit files after a reboot, really need to get the fix for overwriting the monitor.properties file that's in my PR, any idea when it might get reviewed/accepted? |
Beta Was this translation helpful? Give feedback.
A couple of answers here
The startup options can also be set but I am not sure what options you will need to add there.