XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Identify job from notification email

    Scheduled Pinned Locked Moved Backup
    19 Posts 5 Posters 4.1k Views 4 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      Dercni @manilx
      last edited by

      @manilx

      Tried both and both have the same reports

      1 Reply Last reply
      Reply Quote 0
      • P
        ph7 @ph7
        last edited by

        @McHenry
        This is with the Shorter backup reports disabled:

        Screenshot 2025-01-02 at 11-18-51 (3) Inkorg jake.blues@protonmail.com Proton Mail.png

        D 2 Replies Last reply
        Reply Quote 0
        • D
          Dercni @ph7
          last edited by

          @ph7

          Thank you. Let me try that.

          1 Reply Last reply
          Reply Quote 0
          • D
            Dercni @ph7
            last edited by

            @ph7

            OK, I see the difference.

            When an individual VM fails to backup the report is as your shown above and displays the name of the VM however when the job fails as a whole the report inly includes the top section that has a Job ID & Run ID so no way I can see to identify where this job.

            i.e.

            3357a537-55c4-40de-944a-dfe47458b6fb-image.png

            @olivierlambert
            Could these reports include both the pool name and host name in addition to the Job ID and Run ID?

            1 Reply Last reply
            Reply Quote 0
            • olivierlambertO
              olivierlambert Vates 🪐 Co-Founder CEO
              last edited by

              Yes, it should be possible, even if the name can be changed (it's not "stable" vs an UUID). But it makes sense, asking @pdonias about this.

              D 1 Reply Last reply
              Reply Quote 0
              • D
                Dercni @olivierlambert
                last edited by

                @olivierlambert

                Good point, the UUID of the host or pool would also work.

                1 Reply Last reply
                Reply Quote 0
                • olivierlambertO
                  olivierlambert Vates 🪐 Co-Founder CEO
                  last edited by

                  It has been added to the backlog, thanks!

                  D 2 Replies Last reply
                  Reply Quote 1
                  • D
                    Dercni @olivierlambert
                    last edited by

                    @olivierlambert

                    Whilst this request awaits implementation. If I check all hosts individually however I identify the host based upon the jobID or runID from the notification?

                    1 Reply Last reply
                    Reply Quote 0
                    • olivierlambertO
                      olivierlambert Vates 🪐 Co-Founder CEO
                      last edited by

                      Question for @MathieuRA

                      D 1 Reply Last reply
                      Reply Quote 0
                      • D
                        Dercni @olivierlambert
                        last edited by

                        @olivierlambert

                        Is this listed on GitHub so I can track any discussion/progress?

                        I am keen to see this implemented as currently we receive backup reports of failed jobs and have no idea which host is came from.

                        1 Reply Last reply
                        Reply Quote 0
                        • D
                          Dercni @olivierlambert
                          last edited by

                          @olivierlambert

                          Still trying to identify the owner of a job so the I can determine which backup job failed. The email report does not identify the host/pool. Accordingly, I need to login to every individual XO/XOA and check the backup log manually to find the failed job.

                          d817a0bb-cd6a-4cdb-9413-363106f4ca9f-image.png

                          lsouai-vatesL 1 Reply Last reply
                          Reply Quote 0
                          • olivierlambertO
                            olivierlambert Vates 🪐 Co-Founder CEO
                            last edited by

                            Ping @lsouai-vates

                            1 Reply Last reply
                            Reply Quote 0
                            • lsouai-vatesL
                              lsouai-vates Vates 🪐 Product team @Dercni
                              last edited by

                              @McHenry hello, thanks for the report.
                              Can you open a suggestion on Github so we can plan it or next roadmap?
                              Have a good day.

                              1 Reply Last reply
                              Reply Quote 1

                              Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                              Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                              With your input, this post could be even better 💗

                              Register Login
                              • First post
                                Last post