So with apache you’ve got a bunch of options, but basically you’ll want to plugin to whatever Monitoring systems you’re already using for your HPC infrastructure.
We do use Google Analytics for pulling historic things like monthly reports. We use Splunk if need to do something a little more ad-hoc both in real-time or historic, so we’re indexing the apache logs. We’re currently using ganglia for a little bit of graphing, but are shortly going to switch to a prometheus stack for graphinga and alerting at some point. All of these require you to buy into that stack, a Splunk subscription or the Prometheus infrastructure, etc. If you already have these things, cool!
If not, you may try netdata with the apache plugin.This is a install just on the OOD webserver so you don’t need a larger by in to other stacks. Looks like you can even set it behind apache for authentication. (This is just my suggestion because I’ve found netdata super helpful in the past running Apache stacks. I haven’t heard of other folks running it - we at OSC don’t - but again, in the past, in other projects it was super helpful. It’ll give you concurrent connections, request per second, CPU, memory, all in very nice graphs without having to install and maintain other infrastructure).
Other than that, a quick google search of “apache log parser bash” came up with some results. Those could be simple enough to use to achieve what you need. Like a simple
netstat -ant | grep -c ESTAB every 30 or so seconds may give you good baseline, or at least it’s some data easily obtained.
(As an aside, thanks for the question, because it looks like we have no documentation on how to monitor OOD so I’ve created this ticket for that!)