Notice about Panther no longer writing to certain databases

Hi team,

We want to let you know that Panther will stop writing to three databases on July 20, 2026. The data written to each of these databases is already concurrently being written to a new location, and from July 20th onward, you should only reference its new location (unless you are querying historical data from its original location).

No databases, tables, or data will be removed—the three databases that will stop receiving updates will still hold historical data and be available for querying indefinitely.

The databases that will stop being written to on July 20, 2026 are:

• panther_rule_matches

  • Each match on a detection is now also written to panther_signals.correlation_signals (in Search, this is represented by the Signals database and Signals table).

• panther_rule_errors

  • Each detection error is now also written to panther_signals.correlation_errors (in Search, this is represented by the Signals database and Signals Errors table).

• panther_views

  • The panther_views table will be removed on July 20, 2026 and will no longer be queryable.

  • The panther_signals.correlation_signals table replaces panther_views.all_rule_matches.

  • The panther_signals.correlation_errors table replaces panther_views.all_rule_errors.

  • Panther’s Search and Data Explorer tools make it possible to search across multiple types of logs, Lookup Tables/custom enrichments, cloud accounts, and monitoring sources, making panther_views.all_logs, panther_views.all_lookups, panther_views.all_cloudsecurity, and panther_views.all_monitoring unnecessary.

Please let us know if you have any questions or concerns.