Details

    • Type: Epic
    • Status: Open
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 2.X
    • Component/s: Builds
    • Labels:
      None
    • Epic Name:
      Set PMM version to exporters

      Description

      Hi,

      I am debugging some long term issue and look at PMM logs I see:

      time="2018-10-03T18:39:30-04:00" level=info msg="Starting mysqld_exporter
      (version=, branch=, revision=)" source="mysqld_exporter.go:296"
      time="2018-10-03T18:39:30-04:00" level=info msg="Build context
      (go=go1.10.1, user=, date=)" source="mysqld_exporter.go:297"
      time="2018-10-03T18:39:30-04:00" level=info msg="HTTPS/TLS is enabled"
      source="mysqld_exporter.go:366"
      time="2018-10-03T18:39:30-04:00" level=info msg="Enabled High Resolution
      scrapers:" source="mysqld_exporter.go:380"
      time="2018-10-03T18:39:30-04:00" level=info msg="
      --collect.info_schema.innodb_metrics" source="mysqld_exporter.go:382"

      This shows version branch etc zero for MySQL Exporter

      I would like us to make sure we clearly specify version which we use as
      well as with which PMM version it was shipped

      For example it could be version="0.17-pmm-1.14.0" to identify it is 0.17
      community upstream which we shipped with pmm 1.14

      Otherwise it is not possible from the log file to really see when exporter
      was upgraded.


      Peter Zaitsev, CEO, Percona

        Smart Checklist

          Attachments

            Activity

              People

              • Assignee:
                roma.novikov Roma Novikov
                Reporter:
                pz Peter Zaitsev
              • Votes:
                1 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: