Uploaded image for project: 'Percona Monitoring and Management'
  1. Percona Monitoring and Management
  2. PMM-504

Add the ability to rename a node after it has already accumulated data

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Done
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.1.2
    • Component/s: PMM Client
    • Labels:

      Description

      We currently use ansible_fqdn in the playbook that automates the addition of nodes to PMM. This poses a few issues:

      • the hostname may have no resemblance to the CNS entry -> confusion
      • the hostname cannot be resolved by ansible -> localhost.localdomain -> confusion
      • the customer wants the host labelled differently

      Currently there is only the option to remove and add back the node with a different name, thus losing visibility of the already accumulated data.

      Adding pmm-admin rename <existing name> <new name> or similar would allow the Consul and QAN data to be "fixed". Loss of Prometheus data would need to be accepted in such a use-case

      Before renaming : re-check if User ready to rename and lost previous data on Graph (Y/n) and --force-rename option to rename without asking confirmation

        Smart Checklist

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  nailya.kutlubaeva Nailya Kutlubaeva
                  Reporter:
                  ceri.williams Ceri Williams
                • Votes:
                  2 Vote for this issue
                  Watchers:
                  6 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: