Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-47035

System Event Log - Backup Service

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Done
    • 7.0.0
    • 7.1.0
    • tools

    Description

      In Neo we're introducing a system event log to record events that happen across the cluster, see the parent (MB-46215) for more details. 

      For backups we need to capture the following events. 

      Backup Service Events Additional Details Needed
      Backup Deleted UUID of Backup
      Backup Merged UUID of Backup
      Backup Paused UUID of Backup
      Backup Plan Created UUID of Backup Plan
      Backup Plan Deleted UUID of Backup Plan
      Backup Process Crash Name of process that crashed
      PID of crashed process
      Backup Repo Archived UUID of Backup Repo
      Backup Repo Created UUID of Backup Repo
      Backup Repo Deleted UUID of Backup Repo
      Backup Repo Imported UUID of Backup Repo
      Backup Restored UUID of Backup
      Backup Task Completed UUID of Backup Task
      Backup Task Failed UUID of Backup Task
      Backup Task Started UUID of Backup Task
      Backup Settings Changed Previous Setting and New Setting

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            hareen.kancharla Hareen Kancharla added a comment - ns_server System event log, Design Document: https://docs.google.com/document/d/1dMkRVbJFQbGE0cfJl05lYN6qtv_jDv7YEdUfFzQGMbo/edit
            james.lee James Lee added a comment -

            Hi Ian McCloy,

            Just a quick update, I wanted to get your opinion on the events I was planning to log.

            I was planning to implement the following event types:

            • SettingsChanged
            • PlanCreated
            • PlanUpdated
            • PlanDeleted
            • TaskStarted
            • TaskCompleted
            • TaskFailed
            • RepoCreated
            • RepoDeleted
            • RepoArchived
            • RepoImported
            • RepoPaused
            • RepoResumed

            This means, out of the list you provided, the "missing" events will be:

            • Backup Deleted (covered by TaskStart/TaskCompleted)
            • Backup Merged (covered by TaskStart/TaskCompleted)
            • Backup Process Crash (should be handled by ns_server)
            • Backup Restored (covered by TaskStart/TaskCompleted)

            Please can you let me know if this is OK?

            Thanks,
            James

            james.lee James Lee added a comment - Hi Ian McCloy , Just a quick update, I wanted to get your opinion on the events I was planning to log. I was planning to implement the following event types: SettingsChanged PlanCreated PlanUpdated PlanDeleted TaskStarted TaskCompleted TaskFailed RepoCreated RepoDeleted RepoArchived RepoImported RepoPaused RepoResumed This means, out of the list you provided, the "missing" events will be: Backup Deleted (covered by TaskStart/TaskCompleted) Backup Merged (covered by TaskStart/TaskCompleted) Backup Process Crash (should be handled by ns_server) Backup Restored (covered by TaskStart/TaskCompleted) Please can you let me know if this is OK? Thanks, James

            Build couchbase-server-7.1.0-1464 contains cbbs commit 48b650d with commit message:
            MB-47035 Add support for logging system events

            build-team Couchbase Build Team added a comment - Build couchbase-server-7.1.0-1464 contains cbbs commit 48b650d with commit message: MB-47035 Add support for logging system events

            Build couchbase-server-7.1.0-1485 contains cbbs commit 65b9c74 with commit message:
            MB-47035 Update the tools-common dependency

            build-team Couchbase Build Team added a comment - Build couchbase-server-7.1.0-1485 contains cbbs commit 65b9c74 with commit message: MB-47035 Update the tools-common dependency
            ianmccloy Ian McCloy added a comment -

            Hello James,

            Is it not possible to keep the 3 items (Backup Deleted, Merge, Restore) split out into their own unique event IDs ?
            The way you've proposed doing this makes the feature less valuable as an administrator now needs to read and parse the message to know which of these events have happened. The goal is to make sure that admins can use automated tools with unique ids for their monitoring.

            ianmccloy Ian McCloy added a comment - Hello James, Is it not possible to keep the 3 items (Backup Deleted, Merge, Restore) split out into their own unique event IDs ? The way you've proposed doing this makes the feature less valuable as an administrator now needs to read and parse the message to know which of these events have happened. The goal is to make sure that admins can use automated tools with unique ids for their monitoring.
            owend Daniel Owen added a comment -

            Hi Ian McCloy,
            I have created the bug MB-48921 to track the request.

            owend Daniel Owen added a comment - Hi Ian McCloy , I have created the bug MB-48921 to track the request.
            ianmccloy Ian McCloy added a comment -

            Thanks Dan

            ianmccloy Ian McCloy added a comment - Thanks Dan

            Automation is done - jobs running on jenkins and results available on greenboard

            arunkumar Arunkumar Senthilnathan added a comment - Automation is done - jobs running on jenkins and results available on greenboard

            People

              james.lee James Lee
              ianmccloy Ian McCloy
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty