Source: apachedex
Maintainer: Arnaud Fontaine <arnau@debian.org>
Uploaders: Python Applications Packaging Team <python-apps-team@lists.alioth.debian.org>
Section: utils
Priority: optional
Build-Depends: python-setuptools,
               python,
               dh-python,
               debhelper (>= 12)
Standards-Version: 4.3.0
Homepage: https://lab.nexedi.com/nexedi/apachedex
Vcs-Browser: https://salsa.debian.org/python-team/applications/apachedex
Vcs-Git: https://salsa.debian.org/python-team/applications/apachedex.git

Package: apachedex
Architecture: all
Depends: ${misc:Depends},
         ${python:Depends},
         libjs-jquery,
         libjs-jquery-ui,
         libjs-jquery-flot,
         libjs-jquery-flot-axislabels
Description: Compute APDEX from Apache-style logs
 APacheDEX parses Apache-style logs and generates several statistics
 intended for a website developer audience:
 .
   * APDEX (Application Performance inDEX, see http://www.apdex.org) ratio
     (plotted) because you want to know how satisfied your users are.
 .
   * hit count (plotted) because achieving 100% APDEX is easy when there
     is nobody around.
 .
   * HTTP status codes, with optional detailed output of the most frequent
     URLs per error status code, along with their most frequent referers
     because your forgot to update a link to that conditionally-used
     browser compatibility javascript you renamed.
 .
   * Hottest pages (pages which use rendering time the most) because you
     want to know where to invest time to get highest user experience
     improvement.
 .
   * ERP5 sites: per-module statistics, with module and document views
     separated because module and document types are not born equal in
     usage patterns.