Skip to content
- Alerting — create alert rules that watch database activity and notify you when it matches. Build match or threshold rules over fields like user, query type, table and column, masked-data access, denials, and volume; assign a severity; and deliver notifications to email, Slack, Microsoft Teams, PagerDuty, Splunk, ServiceNow, and other webhooks. Alerting works on both Snowflake and OLTP, and is notification-only (it does not block queries).
- Snowflake Native conditions in compound rulesets — you can now add Snowflake’s privacy and semantic categories as conditions in the compound ruleset builder, combined with regex, Google DLP, and other condition types using AND/OR/NOT logic. Available for Snowflake.
- Column content conditions — classifiers can match on the content format detected in a column, including JSON, XML, CSV, Base64, PDF, Microsoft Office documents (DOCX, XLSX, PPTX), RTF, images (PNG, JPEG, GIF, TIFF), archives (ZIP, GZIP), and Parquet. Select one or more formats and set a minimum match threshold.
- Automatic tagging for ALTR Native jobs — automatic tagging now applies tags from ALTR Native classification results, in addition to Google DLP and Snowflake Native. Classifier name matching is now case-insensitive.
- Compound rulesets on Databricks — Google DLP classification jobs on Databricks now evaluate compound rulesets with decision lineage.
- PostgreSQL SCRAM authentication — the OLTP sidecar now supports SASL/SCRAM-SHA-256, allowing ALTR to proxy PostgreSQL databases that require SCRAM authentication.
- Audit records now include additional detail across database engines, including the original client hostname for SQL Server and application name and connection identifiers for MySQL.
