Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-1824

Audit profiler metrics

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • QA Risk Assessment:
      Needs Assessment

      Description

      Throughout Puppet as well as the PuppetDB termini and other termini (e.g. the NC node terminus) we make a lot of Puppet::Util::Profiler.profile calls. In Puppet Server, each one of these creates a dropwizard/metrics metric. We ultimately end up creating multiple metrics for every resource, every certname, every environment, every query. In many cases, this granularity of metrics isn't needed or used. In other cases, we don't actually have any idea what we are timing with these metrics. We should go through the profiler metrics and audit them to understand better what we are gathering metrics on, whether these metrics are useful, and what these metrics mean.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              ruth Ruth Linehan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:

                  Zendesk Support