I agree, but I would point out that only a certain portion of data is exposed from the Messaging module: for example, an API-M call that succeeds can be emitted as an API-M call made and an API-M call that completed (the fact that these are the same call would have to be inferred somehow). But the same call, failing, would show up just as an API-M call made. Why did it fail? It's not clear to me that you could learn that by examining the JMS evidence.
It all depends on what you're going to _do_ with the data-- what questions are going to be asked and what kinds of answers will be useful. It also suggests that it might be interesting to think about what new kinds of information might be useful to emit asynchronously from core repository services. --- A. Soroka Online Library Environment the University of Virginia Library On May 25, 2011, at 4:56 PM, Scott Prater wrote: > This seems like a good use for the Fedora JMS message producer, too: > set up a listener for Fedora API-A and API-M events, then hand those > events off to a bean counter that stores the data in a database, or a > file, or... > > -- Scott > > On 05/25/2011 09:34 AM, Stephen Bayliss wrote: >> Hi >> >> As part of the PIRUS2 project [1] we are examining approaches to collecting >> usage statistics from Fedora repositories. >> >> We are interested in hearing of existing approaches to this topic. Do you >> collect usage information? If so, how? >> >> Some methods that I can think of are: >> >> 1) Fedora behind Apache, collecting information from Apache logs giving >> direct Fedora access information >> 2) Fedora front-end behind Apache, collecting information from Apache logs >> giving front-end access information >> 3) Tomcat log files >> 4) Other logging from Fedora front-end applications >> 5) Collecting information directly from Fedora logs >> 6) Use of services such as Google Analytics >> >> Any experiences of, or thoughts on, any of the above methods would be most >> useful, together with anything not covered by the above. >> >> Currently Fedora doesn't log access attempts apart from in the Fedora log >> file, which may not be ideal as the format of this may change over time, >> since it is not by design logging access attempts in a standard format I >> believe. Any correction on this point most welcome! >> >> Fedora management requests can be collected as part of the messaging module. >> One potential is to extend messaging to encompass access requests so these >> can be collected by a suitable messaging client. Another option would be to >> build access logging directly to a file within Fedora. Any thoughts on >> developing either/both of these would be most welcome; either as an add-on >> module or within core code. >> >> Regards >> Steve >> >> >> >> [1] http://www.cranfieldlibrary.cranfield.ac.uk/pirus2/tiki-index.php >> >> >> ------------------------------------------------------------------------------ >> vRanger cuts backup time in half-while increasing security. >> With the market-leading solution for virtual backup and recovery, >> you get blazing-fast, flexible, and affordable data protection. >> Download your free trial now. >> http://p.sf.net/sfu/quest-d2dcopy1 >> _______________________________________________ >> Fedora-commons-users mailing list >> Fedora-commons-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/fedora-commons-users > > > -- > Scott Prater > Library, Instructional, and Research Applications (LIRA) > Division of Information Technology (DoIT) > University of Wisconsin - Madison > pra...@wisc.edu > > ------------------------------------------------------------------------------ > vRanger cuts backup time in half-while increasing security. > With the market-leading solution for virtual backup and recovery, > you get blazing-fast, flexible, and affordable data protection. > Download your free trial now. > http://p.sf.net/sfu/quest-d2dcopy1 > _______________________________________________ > Fedora-commons-users mailing list > Fedora-commons-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/fedora-commons-users ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ Fedora-commons-users mailing list Fedora-commons-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-users
