Monte Carlo Reviews & Product Details

In my case, and by my use case... I like the monitoring and alerting features... having these set up super easy with just a sql query its the best for me... after this I love having the ability to create incidents or different things just setting up the audiences... I personally just use slack and incident.io, but Im thinking on exploring more capabilities in here... I like that I can customize these super easy and even snooze or get instant feedback on if the set up works or not... specially at the early days when an alert its set up that we get false positives, gets noisy, etc while tuning... super fast and reliable because I can also use it to trace back to other tools that might be affected for different factors. For my specific use case its super helpful and valuable, was easy to navigate and understand because every single feature its explicitly shown in the UI. Another good thing is that the onboarding on the platform was natural, not tricky or complicated at all at least for my use cases... also navigating through the alerts its super intuitive. Honestly I don't know because Im not the one paying, I don't know the money cost of this platform, Im a user and I like it Review collected by and hosted on G2.com.

the only thing is not having the ability to test the descriptions of the alerts in the final destination without an actual alert being triggered, or at least I havent found a way... The descriptions messages to the audience receiving the alert, are set up in a format, specially for KPI's, to see the final result for example in slack I need to trigger it to see it... I'll love to have the ability to just "trigger the alert as a test" to see how it looks like... maybe we already have that and I just don't know yet. I've heard the AI assistant its good for these cases but haven't give it a try yet... Review collected by and hosted on G2.com.

The biggest win for us has been consolidating pipeline oversight into one place instead of piecing it together manually. We run a mix of automatic monitors that cover large groups of tables out of the box, plus more targeted ones we've configured for the checks that matter most to our business — and Snowflake integration was straightforward, so we were getting real coverage within days, not weeks.

The UI makes it easy to set up and adjust monitors ourselves without needing an engineer to write custom scripts every time, segmenting a metric by a business dimension takes minutes, and that's saved us real time compared to chasing down issues after the fact. Alerts routing directly to email and Teams means the right people find out immediately rather than complaints coming from downstream data consumers.

An unexpected benefit: the tuning suggestions have helped us cut down on noisy alerts over time, so the team trusts what it sees. Combined with straightforward performance (monitors run reliably on schedule without adding load we have to babysit), it's given us a level of confidence in our data that's been worth the investment. The ROI on the tool is great for our team and data size spanning 10s of terabytes. Review collected by and hosted on G2.com.

The main friction we've run into is monitor upkeep as our data models evolve — when a table gets moved, renamed, or restructured upstream, monitors pointing at the old location start erroring out until someone manually reassigns them to the right domain. It's not a dealbreaker, but it means someone has to periodically audit for stale or broken monitors rather than the system flagging that drift proactively.

We've also ended up with some overlapping monitors over time as we iterated on configurations — nothing that breaks anything, but it means occasional cleanup to keep things tidy. A clearer "this monitor is now redundant with that one" nudge would help, similar to how tuning suggestions already help with noisy alerts. Review collected by and hosted on G2.com.

I really appreciate the ML monitoring for freshness and volume. It's great because it's super easy to set up and works with a high degree of accuracy. The data quality dashboard is another feature I like. It allows customers to see the current state at a glance, which is very helpful. Monte Carlo also saves us time with its quick setup process, and having all our data quality tests in one place is definitely a plus. Review collected by and hosted on G2.com.

I would love to see more customization be available at a dashboard level and the ability to push dbt test results into it. Review collected by and hosted on G2.com.

Rich functionality and maturity in data observability space. Ease of use and easy to integrate with any data sources. MC helps to check our data assets can be trusted. By integrating various tools / pipelines, MC provides single window to monitor our data assets. Its rich UI and functionality ensures that tool can be easily used by developers or end-users. Highly recommended and much needed tool if trustworthy data is essential in an organization. Review collected by and hosted on G2.com.

Access model can be improved. For now, only developers access MC. Secondly data quality option can be improved with some additional options e.g. duplicate checks etc., Review collected by and hosted on G2.com.

Recently, Monte Carlo introduced a feature that automatically makes all tables available by default, eliminating the need for manual onboarding. Additionally, it now supports direct integration with ServiceNow, enabling incidents to be created automatically whenever a data anomaly is detected. Review collected by and hosted on G2.com.

I expect Monte Carlo to introduce a parent alert feature that groups related alerts together. Additionally, this capability should extend to the ServiceNow integration, allowing incidents created by Monte Carlo to be consolidated under a single parent incident when they are related. Review collected by and hosted on G2.com.

The biggest value for us has been Monte Carlo's automated monitors. Instead of hand-writing freshness and volume checks for hundreds of Snowflake tables, the ML-based detectors learn normal patterns and alert us on anomalies automatically — this caught a stalled pipeline load hours before our business stakeholders would have, and saved us from reporting on stale numbers.

The dbt and Snowflake integrations were quick to connect and are a core part of our daily workflow. End-to-end lineage is the feature I rely on most: when an alert fires, I can trace it from the downstream table back through the dbt models to the exact upstream source in a couple of clicks, which has cut our root-cause investigation time from hours to minutes.

On UI/UX, the incident view and Slack alerting keep the whole data team in the loop without anyone having to log in and dig around — alerts land in our channels with enough context to triage right away. Performance has been solid even across our larger warehouses, and the monitors run without us having to manage any extra infrastructure.

In terms of ROI, the time we save on building/maintaining custom data quality checks and on faster incident resolution has easily justified the cost. Onboarding and support were smooth — the team helped us get our key tables monitored quickly, and an unexpected benefit has been how the lineage and monitoring have improved data trust across the org, so stakeholders rely on the data more and we field fewer "is this number right?" questions. Review collected by and hosted on G2.com.

The biggest pain point for us is pricing and credit consumption. Some features, like certain monitors and the PR/CI integrations, burn credits in ways that aren’t always clear up front. Because of that, we’ve had to regularly review what’s actually being used and disable integrations we rarely rely on just to keep costs in check. Clearer, more predictable visibility into per-feature costs would help a lot.

The automated monitors can also be noisy at first. During the initial learning period, we saw a fair number of false-positive alerts, which meant manual tuning and some effort to set sensible thresholds before the signal-to-noise ratio improved.

On the UI/UX side, moving between lineage, monitors, and incident details can take a lot of clicks. The interface also has a bit of a learning curve for newer team members, especially those who don’t use it every day.

Finally, custom/SQL-based monitors are powerful, but they’re not as intuitive to set up as the out-of-the-box options. Getting solid coverage for sources outside the main warehouse, versus our core Snowflake/dbt tables, also takes more effort. None of these are dealbreakers, but they’re the areas where we’d most like to see improvement. Review collected by and hosted on G2.com.

I find Monte Carlo extremely useful for alerting and data exploration. The ability to check the query that generates a BigQuery table helps me understand the data definition better and aids in debugging. I appreciate how it integrates with our GitHub repo, and we use the Monte Carlo CLI in our CI/CD pipeline to maintain alerts. The custom SQL alerting is particularly valuable since we have a lot of customized metrics to check. The setup process was straightforward, especially with the support I received from my teammate in integrating it with GitHub actions. Review collected by and hosted on G2.com.

I don't have any specific issues with Monte Carlo that I know of right now. I haven't tried Monte Carlo MCP if it exists, but it would be great if the AI agent could access all the information for me. Outside of that, there's nothing I'm currently aware of that needs improvement. Review collected by and hosted on G2.com.

Monte Carlo's ability to be proactive with its recommendations and find anomalies you don't even know to look for. Plus its AI capabilities make setup and troubleshooting a breeze, it does all the work for you. Review collected by and hosted on G2.com.

While Monte Carlo's AI and ML capabilities are strong, they need to spend a little more time on the UI to be a bit more user friendly. Their billing/credit logic is extremely complicated to understand and predict. The amount of historical data used in their algorithm is a lot lower than others in the market and are unable to perform seasonality of data because of it. Review collected by and hosted on G2.com.

Monte Carlo gives us confidence in the reliability of our data by making incidents easier to detect, investigate, and understand. I especially like how it centralizes freshness, quality, lineage, and alerting in one place, so teams can quickly see what broke, what was impacted, and where to focus. It helps reduce the time spent manually chasing data issues and makes data reliability feel much more operational and measurable. Review collected by and hosted on G2.com.

Monte Carlo is powerful, but it can sometimes feel noisy or hard to tune, especially when monitors generate alerts that are technically correct but not always actionable. The investigation workflows are useful, though they can require context from outside Monte Carlo to fully understand root cause. I’d also like clearer guidance on monitor configuration and prioritization so teams can focus more easily on the highest-impact data reliability issues. Review collected by and hosted on G2.com.

Monte Carlo has transformed how we manage data reliability & Observability. Before adopting to it , we spent hours chasing broken pipelines and missing records. Now, issues are flagged in real time, with clear incident detection, triage workflows, and root cause analysis the helps us resolve them faster. The data lineage view makes it easy to see downstream impact, and the integrations with our existing stack were smooth. The dashboards give leadership confidence in the accuracy of our reporting, and the freshness and volume monitoring ensure we don't miss silent data issues. It's a platform that saves us time, reduces risk, and build trust in our analytics. Review collected by and hosted on G2.com.

Initial setup takes some effort, alerts can be noisy at first, some advanced features like lineage and triage require extra training to fully leverage. Review collected by and hosted on G2.com.