-
Notifications
You must be signed in to change notification settings - Fork 0
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
leverage rsyslog for data usage and server issues #30
Comments
@steviewanders @n-a-t-e this may interest you |
I had heard of this, thanks for writing up an issue. I wonder if the combined logs give us anything useful over the regular Apache/Nginx logs from outside the container. tomcat for example is notoriously verbose and uninformative at the same time. |
Thanks @fostermh I'm not sure from which log comes from those ACCESS lines but those are each url request made to erddap. Not sure if that more helpful than Apache/Nginx. FIY this is replicating the erddap-docker feature presented here: |
Getting usage stats from erddap is a sprint topic coming up for the cioos development team. I have done some work on this already so it would be good to collaborate on this. We can definitely try scraping the combined erddap logs and compare to the apache/nginx only method. I have some software in place already to do this but need to remember where I got to with it. |
@fostermh sounds good this all that have done so far (essentially copied what's suggested by erddap-docker Happy to help figure out the rest. |
The latest changes brought in a new
erddap-log
service based on the docker-erddapThis service combines together the three different logs from tomcat, erddap and access logs to the
stdout
output, while adding a timestamp and a tag that relates to the source of each entries. See example below:This seems pretty useful and could be handy for tracking the usage of ERDDAP and/or many other aspects.
Right now, rsyslog outputs stdout. We could potentially output to files.
The text was updated successfully, but these errors were encountered: