When a user opens a PR, they will now receive a message from MC bot that displays an impact analysis of the PR, where we show a summary of directly impacted models, downstream impacted models, and impacted BI reports. Impacted key assets will show stars next to them. Users can expand to see full list as well as click into MC UI from any of the listed assets.
When logging in at https://getmontecarlo.com/signin, users now see a single field to input their email or account identifier. The app then serves the user the appropriate SSO or password login experience.
This avoids a common issue where users would attempt to log in with a password when SSO had been activated for their account.
Three UI/UX changes have improved user's ability to navigate and interact with Incidents that have associated Jira issues. Users can now:
Inactive Monitors to their channels in Microsoft Teams. Previously, just Slack and Email were supported.
For breached SQL rules, users are now not limited to 500 rows cap when trying to download breached rows. Instead, users can go to the breached rows tab and click on "Run Query and Download CSV" to run the SQL rule live and download up to 10k rows breached.
We previously required customers to have dbt integration before setting up Github integration, to allow mapping from pull requests to models to tables. Now, dbt integration is no longer a prerequisite. All customers that use Github can set up the integration. Customers without dbt integration will still see the most recent PRs in IIQ before the incidents, with the limitation that they will not be able to filter for PRs based on tables or see PRs mapped to the asset page.
When query change is detected for an incident, users can now click on the "compare queries" link at the end of the insight banner on the query logs page to directly compare the pre and post change queries.
Users can now create Custom Auth Groups for the Account Owner and Domains Managers roles. Custom Auth Groups can then be mapped to SSO Groups. Previously, the Account Owner & Domains Managers roles could only be applied through default Auth Groups, which could not be mapped to SSO.
If a user creates or links a Jira issue from an Incident, a log of that activity is passed back to any Slack notifications that were sent out, increasingly visibility.
The status of a custom monitor is now broken down into three categories:
This gives clearer insight into what might be wrong if your monitor has not been operating as desired.
