ASF GitHub Bot logged work on TS-5069:

                Author: ASF GitHub Bot
            Created on: 01/Dec/16 23:21
            Start Date: 01/Dec/16 23:21
    Worklog Time Spent: 10m 
      Work Description: Github user zwoop commented on a diff in the pull 

    --- Diff: proxy/logstats.cc ---
    @@ -1164,16 +1167,64 @@ update_schemes(OriginStats *stat, int scheme, int 
    +// Finds or creates a stats structures if missing
    +OriginStats *
    +find_or_create_stats(const char *key)
    +  OriginStats *o_stats = NULL;
    +  OriginStorage::iterator o_iter;
    +  char *o_server = NULL;
    +  // TODO: If we save state (struct) for a run, we probably need to always
    +  // update the origin data, no matter what the origin_set is.
    --- End diff --
    Did you file a Jira on this?

Issue Time Tracking

    Worklog Id:     (was: 32779)
    Time Spent: 1h 40m  (was: 1.5h)

> logstats: add ability to report stats per user instead of host
> --------------------------------------------------------------
>                 Key: TS-5069
>                 URL: https://issues.apache.org/jira/browse/TS-5069
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Logging, Tools
>            Reporter: Gancho Tenev
>            Assignee: Gancho Tenev
>             Fix For: 7.1.0
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
> We would like to enhance {{traffic_logstats}} with the ability to report 
> stats per user instead of host (from the URI).
> Currently the {{traffic_logstats}} expects a binary squid log format defined 
> in the following ATS log config and aggregates and reports stats per the 
> authority part of the URI ({{host:port}} in an usual use-case)
> {code}
> <Format = "%<cqtq> %<ttms> %<chi> %<crc>/%<pssc> %<psql> %<cqhm> %<cquc> 
> %<caun> %<phr>/%<pqsn> %<psct>"/>
> {code}
> It would be useful for our use-case to be able aggregate and report stats 
> based on the 8th squid log field which is an username of the authenticated 
> client {{%<caun>}}).
> In our use-case we need to aggregate and report stats per 
> CDN-customer-specific-tag. 
> For example the new functionality would allow us to replace {{%caun}} with a 
> random header content {{%<\{@CustomerTagHeader\}cqh>}} and report stats per 
> CDN customer by using a new command line parameter {{--report_per_user}} w/o 
> adding extra fields to the binary squid format log expected by 
> {{traffic_logstats}} and keep it backward compatible with the previous 
> version.

This message was sent by Atlassian JIRA

Reply via email to