After last week's hiatus, we have a double feature.

What's new

• Insights tab: Customers can now download Monte Carlo generated dataset about their warehouse, monitors, incidents and more. The reports are available in the Monte Carlo app under Settings > Insights and are downloaded as CSV files.
• User Roles: Monte Carlo users can now be assigned 4 different roles depending on how much access they need. Roles include Owner, Editor, Viewer and Data Consumer (learn more here). Users can be assigned roles on invite or after the user has set up their account.

Improvements and Fixes

• Improved error reporting when connecting Tableau: To improve the Tableau integration setup flow, we now expose error messages and additional context when we're unable to complete the integration.
• Expose errors when testing SQL rule SQL: When setting up a SQL rule, you can now test the SQL command and view any errors returned inline.

What's next

• Incident IQ: We're revamping the entire incident detail view to provide a more holistic summary of the incident itself along with easy to use tools to help determine root cause and resolve the issue.

After last week's push, the team focused on cleaning up bugs and other smaller fixes.

What's new

• Field Health percentile and mean anomaly detection: Our Field Monitors now actively monitor for percentile and mean anomalies in numerical fields. This increases the coverage of potential anomalies in fields with integers

Improvements and fixes*

• Improved accuracy of data asset counts on Monitors tab: The table on the Monitors tab, which counts tables, views and external tables is now more accurate and accounts for deleted tables
• Display SQL Rule errors: To reduce formatting, permissions and syntax errors when creating SQL Rules, we now display actual error messages and helpful hints on how to properly define the SQL Rule.
• Resolved field metric and distribution anomaly chart bug: A bug causing issues with the way the Y axis count rendered was resolved

What's next

• Monitor creation wizards: The team is hard at work converting the Field Health, Dimension Tracking and JSON Schema monitors into the new wizard style flow used for SQL Rules
• Incident Detail page: We're kicking off a new project to re-invent the home for Incidents with an easy to consume timeline of events, richer comments, and more useful information all in one place

Lots of exciting ships this week!

What's new

• New Custom Monitors summary table and description cards: To make it easier to manage your growing list of Field Health, Dimension Tracking, etc. monitors, all custom monitors can now be managed from a single sortable table. We also redesigned the workflow to create new custom monitors, including descriptive cards that explain what each custom monitor does.
• Multi-warehouse support: For customers with multiple data warehouses, you can now connect them to a single Monte Carlo account. With this feature you can manage and create custom monitors, browse the catalog, view Pipelines and more, all from a single Monte Carlo account.
• Data consumer role: When assigned to a user, the Data Consumer role ONLY has permission to access the Catalog, Pipelines and Dashboard tabs in the Monte Carlo app. This role is ideal for data consumers at your company that would benefit from accessing the catalog and pipelines in Monte Carlo, but do not need access to Incidents, Monitors or Settings.

Improvements and fixes*

• Redshift Field Health percentile support: We now collect percentile data via our Field Health monitors in Redshift, which previously was unsupported.
• CLI multi-warehouse compatibility: We updated the CLI used to deploy Monte Carlo crawlers to support multi-warehouse connections. Learn more here.
• Automatically mute pg_temp* tables in Redshift: To reduce catalog clutter and simplify the lineage graphs, we now automatically mute all pg\_temp tables created by Redshift.

What's next

• Custom monitors workflows: We have more improvements to make to the new custom monitors flow including new builders for each of the custom monitors, advanced sorting and filters in the Custom Monitors summary table and more. Let us know if you have any other feedback!
• Data Insights tab: Our data science team is kicking off a project to allow customers to export data generated by Monte Carlo. Exports include the Key Asset report which calculates an importance score for all tables and views in a warehouse, the Incident Event report which lists all anomaly events and relevant data, and more!

The team shipped some great features last week, with big releases coming soon!

What's new

• SQL Rules builder redesign: We converted the simple form builder for SQL rules into a multi-step wizard to make it easier to write SQL queries and validate the configuration.
• SQL Rule relative comparison: SQL Rules can now be configured to trigger Incidents when the returned row count changes relative to previous returned row counts. This is ideal for detecting data drift, defining complex unique freshness anomalies and more!

What's next

• Monitors flow revamp: We continue to make good progress on releasing a new flow for creating, managing and updating Field Health, Dimension Tracking, SQL Rule and JSON Schema Monitors. We released the revamped SQL Rule creator last week, and will soon release the new Monitors tab design.

Over the last week the team was heads down working on bigger product releases. Exciting updates coming soon!

Improvements and Fixes

• Incident grouping window reduced from 24hrs to 6hrs: To reduce the risk of missed incidents, we reduced the even grouping window from 24 to 6 hours. This means if a new table is added to an incident more than 6 hours after the first recorded event, we will create a new incident.
• Resolved JSON schema query timeout: Some customers were experiencing a timeout with JSON schema monitors which is now resolved. What's next
• Monitors flow revamp: We'll be releasing the new flow for creating, managing and updating SQL Rules this week. Next up, we'll be releasing a new Monitors tab to see all your monitors and create new ones in one place.
• Service Level Indicators: We've started to implement custom SLIs to generate Incidents when specific Freshness, Volume and Field Health monitors thresholds are breached - please reach out to our success team if you're interested in adding specific thresholds to your data monitoring\\

Here's what we've been up to over the last week!

What's New

• Mattermost Notification integration: We now support Mattermost as a destination for Incident Notifications
• Back-end Pipelines table node filters: To reduce clutter in the pipelines view, we can now filter specific types of nodes (temp tables, views, etc) - these filters can only be enabled by the Monte Carlo team so please reach out if you're interested\\
• Auto hyperlink Tag URLs: Urls added as tags will now convert to hyperlinks to make it easy to link to external web resources and email addresses Improvements and Fixes
• Redshift crawler bugs: Resolved 2 bugs with our Redshift crawlers where query logs were being misattributed between a staging <> production database, and a # symbol syntax was causing parsing errors
• Improved API docs: We revamped the Monte Carlo API docs to make it much easier to get started with example queries, details on GraphQL introspection, and more\\
• Numerics Field Health monitors enabled by default: Moving forward all field health monitors for numerics like p-values, standard deviation, etc. will be enabled by default What's Next
• Service Level Indicators: We've started to implement custom SLIs to generate Incidents when specific Freshness, Volume and Field Health monitors thresholds are breached - please reach out to our success team if you're interested in adding specific thresholds to your data monitoring\\
• Monitors flow revamp: We're making good progress on releasing a new flow for creating, managing and updating Field Health, Dimension Tracking, SQL Rule and JSON Schema Monitors - we'll release the revamped SQL Rule creator soon

The team shipped a ton of new features and fixes this week. We're excited to hear what you think!

What's New

• Edit Notifications: You can now easily edit Notifications simply by clicking on the pencil icon to the right of the notification
• \\_Search-based dataset and table Notification filters:\\_Easily filter your Incident feed and Notifications using a new search-based dataset and table selector (Search-based Incident filter coming soon!
• Custom freshness monitors: You can now setup custom freshness monitors via our API to check for table writes as often as every 10 minutes (please reach out to our success team for more information!)

Improvements and fixes*

• Added personal token support to Tableau integration: You can now use personal tokens to auth Monte Carlo to connect to your Tableau instance - we also resolved a rendering bug
• Add Looker dashboard links to Reports Affected module: When viewing a table in the Catalog, links to downstream Looker dashboards in the Reports Affected module will now link to the corresponding Catalog view for the dashboard
• Removed 2-step login page: To simplify the log-in experience, we removed the 2 step process which improves compatibility with password managers

What next!

• \\_Service Level Indicators:\\_We've started to implement custom SLIs to generate Incidents when specific Freshness, Volume and Field Health monitors thresholds are breached - please reach out to our success team if you're interested in adding specific thresholds to your data monitorin
• Monitors flow revamp: Our engineering team is incrementally releasing a new flow for creating, managing and updating Field Health, Dimension Tracking, SQL Rule and JSON Schema Monitors - Keep an eye out for the new Monitors summary table coming soon

Here's what we've been up to over the last week at Monte Carlo.

What's New

• Optional row-creation time for Field Health, JSON Schema and Dimension Tracking Monitors: For tables that do not have time series data and are fully re-created on each write, you can now select all records to ensure all records are included in the query\
  Improvements and fixes*
• Increased SSO log-in expiration from 1 hour to 1 day: Customers using SSO will no longer be logged out after 1 hour\
  What's next!
• Service Level Indicators: We're working on the ability to allow customers to define specific thresholds for our Freshness, Volume and Field Health monitors - these SLIs will allow customers to define SLOs and ultimately commit to data SLAs\\
• Monitors flow revamp: Our engineering team is incrementally releasing a new flow for creating, managing and updating Field Health, Dimension Tracking, SQL Rule and JSON Schema Monitors - Keep an eye out for the new Monitors summary table coming soon

Here's what we've been up to over the last week at Monte Carlo.

What's New

• API support for synchronous Monitor Triggers: You can now trigger Monte Carlo Monitors to run via our API - for more information, please reach out to our Success team via email or Slack
• Added creator email address to Notifications: You'll now see the Notification creator's email address listed to provide context on who owns the Notification (Note: Only Notifications created from this point forward will specify creator) Improvements and Fixes
• Improved Catalog Search: The catalog search results now prioritize exact match table names higher resulting in more relevant search results\\
• Improved table pagination UX: Redesigned the pagination arrows for all tables across the Monte Carlo app to improve visibility and usability
• SQL Rule Notification Multi-select bug: Resolved a bug causing the multi-select SQL Rule selector in the Notification set up page to render incorrectly What's next!
• Search-based Dataset filters: Instead of selecting each dataset or table from a list, this refactor will allow you to search and select datasets and tables when creating filters on the Incidents tab and when setting up Notifications
• Service Level Indicators for your data: We're working on the ability to specify thresholds for our Freshness, Volume and Field Health monitors - these SLIs can roll up to SLOs and ultimately help your team commit to data SLAs\\
• Monitors flow revamp: Our engineering team is incrementally releasing a new flow for creating, managing and updating Field Health, Dimension Tracking, SQL Rule and JSON Schema Monitors - keep an eye out for the new Monitors summary table coming soon

Here's what we've been up to over the last week at Monte Carlo.

What's New

• Expanded support for Looker objects in the Pipelines graph: We now show Looker Views, Explores, Looks and Dashboards in lineage\\
• SQL Rule Notifications Routing: You can now route Slack, email, webhook and PagerDuty Notifications by SQL Rule Improvements
• Improved Pipelines graph performance: We now support more complex Pipeline graphs increasing the number of supported objects (tables, views, etc) and paths by 10x
• Smarter event grouping in Incidents: Now when an Incident status is updated to anything besides Investigating, new tables will not be added to the incident to minimize the risk of the new anomalous table silently grouping into a Fixed issue What's next!
• Service Level Indicators: We're working on the ability to allow customers to define specific thresholds for our Freshness, Volume and Field Health monitors - these SLIs will allow customers to define SLOs and ultimately commit to data SLAs\\
• Monitors flow revamp: Our engineering team is incrementally releasing a new flow for creating, managing and updating Field Health, Dimension Tracking, SQL Rule and JSON Schema Monitors - Keep an eye out for the new Monitors summary table coming soon