Uploaded image for project: 'Traffic Server'
  1. Traffic Server
  2. TS-4193

Enabling proxy.config.disable_configuration_modification can "lose" metrics via e.g. stats_over_http

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Manager, Metrics, Plugins
    • Labels:
      None

      Description

      With normal configs, using stats_over_http, I get e.g.

      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",
      

      However, if I disable config write updates (proxy.config.disable_configuration_modification=1), these metrics are no longer producing values via stats_over_http:

      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",
      

      What's surprising is the according to traffic_ctl, the metrics are fine even with the new config enabled:

      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
      

      Maybe these changes interfere with how the stats_over_http plugin uses the lib records iterator?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                bcall Bryan Call
                Reporter:
                zwoop Leif Hedstrom
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: