[ 
https://issues.apache.org/jira/browse/TS-2169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919509#comment-13919509
 ] 

Ron Barber edited comment on TS-2169 at 3/4/14 6:14 PM:
--------------------------------------------------------

I assume you are referring to the loop below?  This get executed by, what I 
will call, a stats collector thread so I guess stats collection could get 
delayed..if this turns out to be an issue we may want to add an option to 
provide the ability to granularly disable portions of ssl stats collection.
{code}
+    for (size_t i = 0; i < ctxCount; i++) {
+      SSL_CTX * ctx = certLookup->get(i);
+
+      sessions += SSL_CTX_sess_accept_good(ctx);
+      hits += SSL_CTX_sess_hits(ctx);
+      misses += SSL_CTX_sess_misses(ctx);
+      timeouts += SSL_CTX_sess_timeouts(ctx);
+    }
{code}


was (Author: rwbarber2):
I assume you are referring to the loop below?  This get executed by, what I 
will call, a stats collector thread so I guess stats collection could get 
delayed..if this turns out to be an issue we may want to add an option to 
provide the ability to granularly disable portions of ssl stats collection.
+    for (size_t i = 0; i < ctxCount; i++) {
+      SSL_CTX * ctx = certLookup->get(i);
+
+      sessions += SSL_CTX_sess_accept_good(ctx);
+      hits += SSL_CTX_sess_hits(ctx);
+      misses += SSL_CTX_sess_misses(ctx);
+      timeouts += SSL_CTX_sess_timeouts(ctx);
+    }


> SSL statistics
> --------------
>
>                 Key: TS-2169
>                 URL: https://issues.apache.org/jira/browse/TS-2169
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: SSL, Stats
>            Reporter: David Carlin
>            Assignee: James Peach
>              Labels: Review
>             Fix For: 5.2.0
>
>
> It would be swell if there were some traffic_line SSL statistic variables.
> For instance, number of SSL connections and SSL bytes.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to