You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Gancho Tenev (JIRA)" <ji...@apache.org> on 2016/11/29 22:54:58 UTC

[jira] [Updated] (TS-5069) logstats: add ability to report stats per user instead of host

     [ https://issues.apache.org/jira/browse/TS-5069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gancho Tenev updated TS-5069:
-----------------------------
    Fix Version/s: 7.1.0

> 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
>
>
> 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
(v6.3.4#6332)