Analyzing EZproxy Logs with ezPAARSE

undefined
 
Analyzing EZproxy logs
with ezPAARSE
 
KAT GREER
GEORGIA GWINNETT COLLEGE
KGREER1@GGC.EDU
 
About Your Logs
 
 
Record of server activity
 
Common Log Format
 
Do you have access?
 
Do you know your LogFormat?
 
A Log Example
 
CONFIG FILE 
(config.txt)
 
LOG FILE 
(ezp20150512.log)
 
 
OCLC Documentation:
 
http://www.oclc.org/support/services/ezproxy/documentation/cfg/logformat.en.html
 
http://www.oclc.org/support/services/ezproxy/documentation/cfg/logfile.en.html
 
ezPAARSE
 
 
Free and open source software
 
GPL-compatible license
 
Developed by COUPERIN (
http://www.couperin.org
) and University of Lorraine
 
2014 LIBER award
 
Documentation: 
http://analogist.couperin.org/ezpaarse/doc/usage_en
 
GitHub: 
https://github.com/ezpaarse-project/ezpaarse
undefined
 
 
Web Application
 
Multi-platform
 
Log Analyzer
 
Parsers
 
 
Wiki Portal
 
Collaborative Space
 
Hosts an ezPAARSE
installation
 
 
Visualization Tool
 
Macro-enabled Workbook
 
Charts and graphs
undefined
 
Image: http://analogist.couperin.org/start_en
undefined
 
An Example Process
 
Analysis
 
BENEFITS
 
 
Locally-created logs
 
On-demand source for usage statistics
 
COUNTER codes of practice
 
Easy to implement
 
Visual representations
 
DRAWBACKS
 
 
Still in development
 
Log files only track off-campus usage
 
Need to generate more PKBs/parsers
 
Buggy software
 
Overall Impressions
 
 
Value of using locally-created logs
 
ezPAARSE software potential
 
Other options
o
AWstats
o
Python scripts
o
Homegrown solution
 
Use data your way
undefined
 
Questions?
Slide Note
Embed
Share

This presentation delves into the analysis of EZproxy logs using ezPAARSE, a free and open-source software with a GPL-compatible license. It covers log formats, examples, benefits, and drawbacks of locally-created logs, offering insights and value for usage statistics. Explore other options like AWstats, Python scripts, or homegrown solutions for handling server activity logs effectively.

  • EZproxy Logs
  • ezPAARSE
  • Log Analysis
  • Usage Statistics
  • Open-Source Software

Uploaded on Oct 08, 2024 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

E N D

Presentation Transcript


  1. Analyzing EZproxy logs with ezPAARSE KAT GREER GEORGIA GWINNETT COLLEGE KGREER1@GGC.EDU

  2. About Your Logs Record of server activity Common Log Format Do you have access? Do you know your LogFormat?

  3. A Log Example CONFIG FILE (config.txt) LOG FILE (ezp20150512.log) OCLC Documentation: http://www.oclc.org/support/services/ezproxy/documentation/cfg/logformat.en.html http://www.oclc.org/support/services/ezproxy/documentation/cfg/logfile.en.html

  4. ezPAARSE Free and open source software GPL-compatible license Developed by COUPERIN (http://www.couperin.org) and University of Lorraine 2014 LIBER award Documentation: http://analogist.couperin.org/ezpaarse/doc/usage_en GitHub: https://github.com/ezpaarse-project/ezpaarse

  5. Web Application Wiki Portal Visualization Tool Multi-platform Collaborative Space Macro-enabled Workbook Log Analyzer Hosts an ezPAARSE installation Charts and graphs Parsers

  6. Image: http://analogist.couperin.org/start_en

  7. An Example Process

  8. Analysis BENEFITS DRAWBACKS Locally-created logs Still in development On-demand source for usage statistics Log files only track off-campus usage COUNTER codes of practice Need to generate more PKBs/parsers Easy to implement Buggy software Visual representations

  9. Overall Impressions Value of using locally-created logs ezPAARSE software potential Other options o AWstats o Python scripts o Homegrown solution Use data your way

  10. Questions?

More Related Content

giItT1WQy@!-/#giItT1WQy@!-/#giItT1WQy@!-/#