Uploaded image for project: 'Subscription Watch'
  1. Subscription Watch
  2. SWATCH-4403

High Level estimation of data storage impact of "always on" usage and host data

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • subs-swatch-thunder

      Task Objective
      Conduct storage capacity research to populate a dedicated section of the epic's research/design document with data storage impact estimates for implementing "Always On" capacity tracking.

      Research Focus
      Estimate the increase in data storage (and associated costs) required to transition from the current opt-in model to "Always On" (100% opt-in equivalent) for capacity-related data.

      Technical Approach
      • Analyze current org_config table (opted-in orgs) vs. total org population
      • Correlate to capacity-related table volumes: events, hosts, host_tally_buckets, tally_snapshots, tally_measurements, etc.
      • Assess data sources: Observatorium, Rhelemeter, HBI
      • Estimate storage scaling requirements for always-on processing

      Key Definition
      "Always On" = Auto opt-in ALL orgs when SWATCH receives data (vs. current filtering by org_config)
      Scope: tally & usage related tables only (not subscription or billing tables)

      Deliverable
      Create a "Storage Usage Impact" section of SWATCH-4367 epic document with:
      • Current vs. projected data volume estimates (by table and data source)
      • Database storage cost impact projections

      Acceptance Criteria
      • Document contains quantified storage impact estimates (current vs. always-on)
      • Include database storage cost projections for increased data volume

              Unassigned Unassigned
              lburnett0 Lindsey Burnett
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: