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

Docker container for `pmm-client`: Option to change behavior and follow sidecar pattern

Details

    Description

      This improvement request comes from this bug: https://jira.percona.com/browse/K8SPXC-585

      Issue:

      If pmm-client cannot connect to pmm-server for any reason (network glitch, wrong password), pmm-client container crashes.

      This means that monitoring server stability can affect the stability of the database cluster.

      Desired behavior:

      Container should not crash, but just throw an error.

      Good example - mongodb-exporter. If it cannot connect to MongoDB database:

      • it still runs
      • on metrics page it tells that it cannot connect to MongoDB and states the reason

      Default entrypoint shouldn't exit with error, but waiting in infinite loop with trying to apply failed commands and provide logs to show issue.

      How to test:

       

      Attachments

        Issue Links

          Activity

            People

              nurlan.moldomurov Nurlan Moldomurov
              sergey.pronin Sergey Pronin
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Smart Checklist