Uploaded image for project: 'Sentry (Retired)'
  1. Sentry (Retired)
  2. SENTRY-872 Uber jira for HMS HA + Sentry HA redesign
  3. SENTRY-1538

Create schema for storing HMS path change and Sentry permission change.

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.0.0
    • 2.0.0
    • Sentry

    Description

      As HMS Follower processes HMS notifications, they should be stored in Sentry DB. At a minimum we can only store notification ID, but for debugging/troubleshooting it is better to store actual JSON notification events as well.

      So this task about adding a schema for storing notifications. It its simplest form it will contain just notification ID as the primary key, possibly timestamp and the JSON notification event.

      Attachments

        Issue Links

          blocks

          Sub-task - The sub-task of the issue SENTRY-1539 HMS Follower should store arriving HMS notifications

          • Major - Major loss of function.
          • Resolved
          is required by

          Sub-task - The sub-task of the issue SENTRY-1608 Converting Sentry to a stateless service

          • Major - Major loss of function.
          • Resolved
          relates to

          Sub-task - The sub-task of the issue SENTRY-1511 HDFS Sync change for handling persisted Sentry delta or full updates

          • Major - Major loss of function.
          • Resolved
          links to

          Web Link Review Board Link

          Activity

            People

              hahao Hao Hao
              akolb Alex Kolbasov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Slack

                  Issue deployment