You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2016/02/11 18:56:18 UTC
[jira] [Created] (TS-4193) Enabling
proxy.config.disable_configuration_modification can "lose" metrics via e.g.
stats_over_http
Leif Hedstrom created TS-4193:
---------------------------------
Summary: Enabling proxy.config.disable_configuration_modification can "lose" metrics via e.g. stats_over_http
Key: TS-4193
URL: https://issues.apache.org/jira/browse/TS-4193
Project: Traffic Server
Issue Type: Bug
Components: Manager, Metrics, Plugins
Reporter: Leif Hedstrom
With normal configs, using stats_over_http, I get e.g.
{code}
loki (10:50) 339/0 $ curl -s http://loki.ogre.com/_bazinga | grep proxy.node.http.user_agent_total
"proxy.node.http.user_agent_total_request_bytes": "789",
"proxy.node.http.user_agent_total_response_bytes": "612070",
{code}
However, if I disable config write updates (proxy.config.disable_configuration_modification=1), these metrics are no longer producing values via stats_over_http:
{code}
loki (10:52) 341/0 $ curl -s http://loki.ogre.com/_bazinga | grep proxy.node.http.user_agent_total
"proxy.node.http.user_agent_total_request_bytes": "0",
"proxy.node.http.user_agent_total_response_bytes": "0",
{code}
What's surprising is the according to traffic_ctl, the metrics are fine even with the new config enabled:
{code}
loki (10:52) 341/0 $ /opt/ats/bin/traffic_ctl metric match proxy.node.http.user_agent_total
proxy.node.http.user_agent_total_request_bytes 1948
proxy.node.http.user_agent_total_response_bytes 1699917
{code}
Maybe these changes interfere with how the stats_over_http plugin uses the lib records iterator?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)