@@ -127,13 +127,19 @@ It's important to note that alert statuses ("Expected", "No action needed", "Fal
After marking alerts as normal, it can take several hours before the new, widened thresholds are visible in the system.
For multiple related alerts, you can use the "Mark all as normal" option in the `Tune model` drop down on the top right of the anomaly chart ([link to docs](https://docs.getmontecarlo.com/docs/tuning-thresholds#training-data)), to avoid clicking through each event individually.
## Note on DWH Permissions
## Schema/Permission Management
In order for Monte Carlo to be integrated with Snowflake, we have had to run the permissions script as specified in the [official docs](https://docs.getmontecarlo.com/docs/snowflake) for each database we needed to monitor.
The same script has to be run as many times as we have databases to monitor (in our case `raw`, `prep` and `prod`) with the correct values for the `$database_to_monitor` variable. The scrips foresees new tables to be added to existing schemas. In case of a new schema the script has to be executed again for the database the schema resides. The data observability user is stored on our internal data vault.
Monte Carlo requires a one-time permissions script to be run for each database it monitors (`raw`, `prep`, `prod`). The script must be re-run any time a new schema is added to a monitored database. Full setup details are in the [official docs](https://docs.getmontecarlo.com/docs/snowflake); the data observability user credentials are stored in our internal data vault.
Please note this is an exception to our usual permission-handling procedure, where we rely on Permifrost, because observability permissions are an edge-case for Permifrost and not yet supported by the tool.
There is an ongoing [feature request](https://gitlab.com/gitlab-data/permifrost/-/issues/120) on Permifrost for adding granularity to the way permissions are set, but no solution has been agreed on yet.
> **Note:** This is an exception to our standard permission-handling procedure. Observability permissions are an edge case not yet supported by Permifrost — there is an open [feature request](https://gitlab.com/gitlab-data/permifrost/-/issues/120) tracking this.
### Adding a schema
Re-run the permissions script for the database the schema resides in, setting the correct value for `$database_to_monitor`. See the [official docs](https://docs.getmontecarlo.com/docs/snowflake) for the full script.
### Removing a schema
Go to **Settings → Ingestion → Monte Carlo Snowflake Warehouse Integration**, search for the schema, and uncheck it.
