[
https://issues.apache.org/jira/browse/TS-4107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15076210#comment-15076210
]
James Peach commented on TS-4107:
---------------------------------
Looks like the original bug did this backwards.
{{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 {{RECT_PROCESS}}.
> 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
>
> {{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)
