GitHub user kxepal opened a pull request:

    https://github.com/apache/couchdb-couch/pull/13

    Validate document update stats

    This adds two new metrics about counting validation rejections and the time 
was spent on running vdu functions. The reason for each inside commit messages.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kxepal/couchdb-couch vdu-stats

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-couch/pull/13.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #13
    
----
commit 223871a41efcc4e5a63ba653410ae354df57565a
Author: Alexander Shorin <kxe...@apache.org>
Date:   2014-10-30T21:40:09Z

    Track the time was spent to execute validate_doc_update function
    
    Validate document update functions are causes significant slowdown on
    request processing time when document gets modified. As more validate
    functions we have as higher delay will and the couchdb/request_time
    metric couldn't tell us why it values are so high and why our service
    is so slow. By tracking down the time spent on running all validate
    functions for each document update we could see this overhead and decide
    just in time if our validation functions are need in some optimizations.

commit 1550d0e3027281d22eb66fc0743d0b57621420d3
Author: Alexander Shorin <kxe...@apache.org>
Date:   2014-10-31T19:13:19Z

    Add stats counter for validate_doc_update rejections
    
    Counting update rejections helps to answer on following questions:
    - What is the origin of so anomaly high 401/403 responses?
      We'll be able to distinguish validation errors from regular auth ones.
    - Is someone trying to do things we disallowed and how often?
      High rejection rate is a good signal to start figure out do we have
      too strict validation conditions or to start looking for bad clients.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to