Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Due to the current gap in continued funding from the U.S. National Science Foundation (NSF), the NSF Unidata Program Center has temporarily paused most operations. See NSF Unidata Pause in Most Operations for details.
Hello, The threddsAccess.log file is in Apache "common" format with the addition of a response time field at the end of each line. So, we use some standard log analyzer software on our motherlode server (awstats and sawmill). Also, I don't think we mentioned this in the 3.14 release notes but we are switching from the above logs rolled by us to the logs produced by the Tomcat AccessLogValve. One really nice thing about this valve is that it knows the size of the responses so the log contains the number of bytes even for OPeNDAP responses. So, if the response size is important, you might think about switching to that as well. We'll add documentation for this in our next release but, for now, here are the basics. You have to set it up in the Tomcat server.xml file. If you search for "Access" in the server.xml file you will find a section on this valve that is commented out. If you just uncomment the Valve element you should get a log in the Apache common format for all requests handled by your Tomcat installation. We changed the log file name and added the response time field to the "common" format. Here's what ours looks like: <!-- Access log processes all requests for this virtual host. By default, log files are created in the "logs" directory relative to $CATALINA_HOME. If you wish, you can specify a different directory with the "directory" attribute. Specify either a relative (to $CATALINA_HOME) or absolute path to the desired directory. --> <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="access." suffix=".log" pattern="%h %l %u %t "%r" %s %b %D" resolveHosts="false"/> Hope that helps, Ethan Park Taezoon wrote: > Dear all, > > I would like to build a web page which shows the statistics of the > data served by THREDDS. The log file generated by THREDDS seems to > have almost all the information necessary inside. > Before start writing THREDDS log analyzer, I would like to check > whether there is one already built. ;-) Do you guys have any > implementation of the log analyzer for THREDDS? > > Thank you. > > Taezoon Park -- Ethan R. Davis Telephone: (303) 497-8155 Software Engineer Fax: (303) 497-8690 UCAR Unidata Program Center E-mail: edavis@xxxxxxxx P.O. Box 3000 Boulder, CO 80307-3000 http://www.unidata.ucar.edu/ --------------------------------------------------------------------------- ============================================================================== To unsubscribe thredds, visit: http://www.unidata.ucar.edu/mailing-list-delete-form.html ==============================================================================
thredds archives: