Query change insights are now available on tables upstream of incident tables, expanding the root cause insights MC can detect from incident table only to further upstream.
Whenever MC detects any query change upstream of an incident, a banner will show up on incident feed and incident IQ pages alerting the insight detection. From the query logs tab in Incident IQ, users will be able to select not only incident tables, but also upstream tables from table selector, to view query change details.
To help eliminate any confusion between the functionality of Monte Carlo versus a more traditional enterprise data catalog, the Catalog tab has been renamed to Assets. There's no change to the functionality or roadmap of that part of the product -- this is merely a design change.
Today we are announcing Monte Carlo's foray into data observability for transactional databases, starting with the ability to run SQL Rules on MySQL, Postgres, and Microsoft SQL Server. SQL Rules can be created in either the UI and/or programmatically via Monitors-as-Code (API/SDK too). These monitors can be used to generate notifications to relevant stakeholders, circuit break pipelines, and conduct RCA (e.g. sampling). Catalog entries are also created in Monte Carlo and Custom Lineage APIs are available to write lineage across databases to data warehouses. Please reach out if you have additional use-cases for these transactional databases!
For customers who have integrated Jira to Monte Carlo, you can now start the flow to convert an Incident to a Jira issue directly from Slack. This increases visibility of this time-saving feature.
Customers with dbt integration can now set up Github integration to gain visibility into the code impact on their data!
The Github integration allows customers to
Follow docs here to set it up https://docs.getmontecarlo.com/docs/github
Users can now filter down the metrics in Data Reliability Dashboard only for tables with a specific tag. Multiple tags can be added and filtered on at a time with each added as an OR condition.
This is particularly helpful when trying to narrow down the tables that are included in some of the metrics in the Data Reliability Dashboard, especially when they are in a specific domain. Rather than creating a separate domain just for reporting purposes, users can now easily filter down by tags to get to the level they want.
Users can now choose which Snowflake Databases and Schemas are ingested into Monte Carlo. This adds onto our existing functionality for BigQuery, Redshift, and Databricks via CLI/API, see docs here.
Slack and Email notifications only. Docs.
Users of Monitors as Code have heavily requested a way to also manage the notifications for their monitors, without going into the UI. This makes that possible, along with all the version control goodness that comes with managing a configuration via code.
Monitor creation for SQL Rules now allows an optional âInvestigation Queryâ to allow users build custom query for incident investigation.
Incident IQ for an SQL Rule breach shows the results of running the investigation query at the time of breach in a new tab called âInvestigation rowsâ
. If the monitor fails while this option is enabled, a failure notification will be sent to same destinations that an Incident notification would be sent to. Read our full doc for more detail.
