[
https://issues.apache.org/jira/browse/TS-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095351#comment-15095351
]
ASF subversion and git services commented on TS-4107:
-----------------------------------------------------
Commit 8e0f81454fd79cc4dde4bba17b4eb38a7f195c0d in trafficserver's branch
refs/heads/master from [~jpe...@apache.org]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=8e0f814 ]
TS-4107: proxy.process.ssl.total_success_handshake_count_in has wrong record
type
proxy.process.ssl.total_success_handshake_count_in should be the
metrics generated in the core SSL code, and the old compatible name
proxy.process.ssl.total_success_handshake_count should be generated
as a custom metric. The custom metric needs to be registered in
RecordsConfig.cc but it should be of type RECT_PROCESS not RECT_NODE.
This closes #409.
> proxy.process.ssl.total_success_handshake_count_in has wrong record type
> ------------------------------------------------------------------------
>
> Key: TS-4107
> URL: https://issues.apache.org/jira/browse/TS-4107
> Project: Traffic Server
> Issue Type: Bug
> Components: Metrics, SSL
> Reporter: James Peach
> Assignee: James Peach
> Fix For: 6.2.0
>
>
> {{proxy.process.ssl.total_success_handshake_count_in}} is the only SSL metric
> registered in {{RecordsConfig.cc}} where it is incorrectly registered as a
> node metric, rather than a process metric.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
