SIT-13751: Hold Activity Logs

How to Use This Feature

Feature Summary: Logging for Hold Operations

Overview

-----------

This feature allows system administrators to monitor and troubleshoot hold-related activities with precision. It provides detailed logs for hold creation, removal, and update events.

Behavior

  • Logs every hold creation event with:

    • + Event or Event Series ID

    + BO Operator ID

    + Seat ID

    + Hold type

    + Timestamp

  • Logs every hold removal event with:

    • + Event or Event Series ID

    + Box Office Operator ID

    + Seat ID

    + Hold type

    + Timestamp

  • Logs every hold update event with:

    • + Event or Event Series ID

    + BO Operator ID

    + Seat ID

    + Old hold type

    + New hold type

    + Timestamp

    Requirements

  • Logs must be written to a centralized, queryable logging system
  • Logs must be structured and consistently formatted for downstream analysis
  • Logging must only occur if the admin is authenticated with valid credentials
  • Include error handling for failed logging attempts
  • Ensure logging does not block or delay the core hold operation

    • Acceptance Criteria

  • Log hold creation event:

    • + Admin is authenticated with valid credentials

    + System logs the hold creation event

    + Log entry includes event or event series ID, admin ID, seat ID, hold type, and timestamp

  • Log hold removal event:

    • + Admin is authenticated with valid credentials

    + System logs the hold removal event

    + Log entry includes event or event series ID, admin ID, seat ID, hold type, and timestamp

  • Log hold update event:

    • + Admin is authenticated with valid credentials

    + System logs the hold update event

    + Log entry includes event or event series ID, admin ID, seat ID, old hold type, new hold type, and timestamp

    Out of Scope

  • UI changes or log viewer interfaces
  • Role-based access control for viewing logs
  • Logging of non-hold seat operations (e.g., purchases, transfers)
  • Historical backfill of hold logs prior to feature implementation

    • Additional Information

    Status: Pending UAT Deployment
    Assigned to: Kevin Campbell
    🏠 Home View in Jira