[
https://issues.apache.org/jira/browse/TS-904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875905#comment-13875905
]
Igor Galić commented on TS-904:
-------------------------------
[~zym] do you mean one of those:
{code}
{RECT_NODE, "proxy.node.log.event_log_error_aggr", RECD_INT, "0", RECU_NULL,
RR_NULL, RECC_NULL, NULL, RECA_NULL}
{RECT_NODE, "proxy.node.log.event_log_access_aggr", RECD_INT, "0",
RECU_NULL, RR_NULL, RECC_NULL, NULL, RECA_NULL}
{RECT_CLUSTER, "proxy.cluster.log.event_log_error_aggr", RECD_INT, "0",
RECU_NULL, RR_NULL, RECC_NULL, NULL, RECA_NULL}
{RECT_CLUSTER, "proxy.cluster.log.event_log_access_aggr", RECD_INT, "0",
RECU_NULL, RR_NULL, RECC_NULL, NULL, RECA_NULL}
{code}
or this stuff from log.xml:
{code}
<Interval = "aggregate_interval_secs"/>
This tag is needed when the format contains any of the aggregate
operators. The "aggregate_interval_secs" value is a number
representing the number of seconds over which the entry is aggregated
before being produced. The valid set of aggregate operators are:
COUNT '*' can be used for the field value
SUM
AVG
FIRST
LAST
{code}
Can you please clarify on the bug, and if it's no longer relevant, please close
it.
> when doing custom logging, it would be nice if we can set dedicate sampling
> rate for each rule
> ----------------------------------------------------------------------------------------------
>
> Key: TS-904
> URL: https://issues.apache.org/jira/browse/TS-904
> Project: Traffic Server
> Issue Type: New Feature
> Components: Logging
> Affects Versions: 3.0.0
> Reporter: Zhao Yongming
> Priority: Minor
> Fix For: sometime
>
>
> the sampling is a global config in logging, we want to get it custom-able.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
