Roadmap: suppression support in dragonfly-mainframe

[import-pandas-as-numpy]

Summary

Roadmap issue for suppression support in dragonfly-mainframe.

Goal

Provide backend support for all three requested suppression scopes:

• package
• rule
• package+rule

Each scope must support:

• permanent suppression
• suppression until a specific date/time

Notes

• Existing issue #258 has been repurposed as the package-scope API task because its original matched-rule-equality semantics conflict with the requested product behavior.
• This roadmap covers the mainframe work needed by the audited codebases. Any external alert producers that consume mainframe data will still need to adopt the resulting suppression state separately.

Execution Order

• dragonfly-mainframe#374 Add suppression persistence model and Alembic migration for package, rule, and package-rule scopes
• dragonfly-mainframe#258 Implement package-scope suppression API with permanent and expiring entries
• dragonfly-mainframe#373 Implement global rule suppression API with permanent and expiring entries
• dragonfly-mainframe#372 Implement package-rule suppression API with permanent and expiring entries
• dragonfly-mainframe#375 Resolve active suppressions during alert/report decisions and expose suppression state to consumers

Requested Scenarios Covered

• Suppress all alerting for requests permanently
• Suppress all alerting for pytest until 2031-01-01
• Suppress exfil_domains only for package lithops