Monte Carlo Reviews & Product Details

I like the ease of use of Monte Carlo, especially how setting up monitoring is very simple. The integration with external tools like Slack and Jira is top-notch, sometimes eliminating the need to go to the Monte Carlo website to interact with an alert for its entire lifecycle. The user interface is generally very user-friendly, with only a few minor exceptions. I also love the quick pace at which the Monte Carlo team responds to issues, bugs, feature requests, and improvement suggestions. Review collected by and hosted on G2.com.

The biggest pain point for me is the lack of possibility to merge alerts from metric monitors into one incident. We often have an issue that triggers many alerts, and we have to manage each alert separately, even though all have the same root cause. Since metric monitors are the backbone of Monte Carlo, it's really frustrating. This has been the case for a year and a half now. Another issue is the too fast and too big changes; I expected more stability at this stage. It's really difficult to keep up with paradigm shifts. For example, the change for Table monitors caused confusion. I recently ingested a big data set only to learn that tables are now monitored by default upon ingestion, which was contrary to previous behavior where you had to set up monitoring manually. Review collected by and hosted on G2.com.

Monte Carlo has a great support team that has been willing to help us with questions and improvement requests. Their product has easy to use out-of-the-box tools like machine learning thresholds that we've found to be helpful as well. We are also experimenting with their agent observability tools which allow you to have better insight into what is really happening in agentic workflows. Review collected by and hosted on G2.com.

My biggest frustration with Monte Carlo is that there isn’t a coding wrapper (Python) I can use. Right now it’s limited to out-of-the-box functionality or SQL, so it’s difficult to implement more in-depth checks. Review collected by and hosted on G2.com.

I love how quickly Monte Carlo is adapting to a changing data world, especially with the rise of AI. They've worked closely with us to set up alerts on Snowflake agents, and I appreciate that they open up office hours for collaboration with their agent experts. It's a centralized location for monitoring our data and notifies us immediately if there's an issue. I really like the integration features, particularly with Slack. Monte Carlo also enables us to get a widescreen picture of how our agents are performing, highlighting areas for improvement. Their support team is easy to reach and quick to respond. Review collected by and hosted on G2.com.

I would love if you could tune models from Slack. It would be great if when you receive the alert you could open and tune the model from inside Slack instead of having to open up the Monte Carlo UI. There were some bumps getting access set up correctly. The error handling is a bit of a black box. You cannot get details on what is happening and why it's not working. Review collected by and hosted on G2.com.

I like Monte Carlo because it's a very complete tool. It provides everything in the platform from data quality alerts, volume, and schema monitoring, all the way to offering a summary of all the alerts within our tables. Additionally, you can set up alerts in different ways including automatic ones with volume freshness and schema monitoring. Plus, it's quite useful to be able to set up personalized alerts. Review collected by and hosted on G2.com.

There are two main issues I have with Monte Carlo. First, is the communication. Monte Carlo does a lot of changes, but we're not always aware of them. This can lead to us doing some work and then having to rework it because there has been a migration or changes in the project that we weren't aware of. The second issue is with their ML monitoring. They set thresholds for alerts based on machine learning, but it's not adjusting well. I can classify alerts as expected, but it doesn't adjust the threshold as much as needed, leading to a lot of false errors. I'm wondering about the point of having those ML thresholds. Review collected by and hosted on G2.com.

I use Monte Carlo for work to ensure our tables are correct and accurate. It helps us validate our tables/data in a timely manner automatically. The benefit is we save time, and it's easy to see an alert. I like that it is easy to use and navigate even for beginners. As someone who has not used a tool like Monte Carlo before and was running notebooks, now Monte Carlo really helps. Monte Carlo is the place where all our monitors sit, and we do not need to look anywhere else. We get timely alerts. The initial setup was pretty easy, just wait time for tables to be loaded. Review collected by and hosted on G2.com.

I think sometimes there are issues with the correct number of rows returned. Monte Carlo gets it wrong sometimes. Not very sure, we have also raised this with the Monte Carlo team. But sometimes it does not populate all alerted rows. Review collected by and hosted on G2.com.

I like the lineage feature in Monte Carlo because it allows me to track data back to its source and see where it's being fed into and from. This feature almost gives me a flow diagram of where data is going, making it easier to isolate various types of data flows. I also appreciate the nice, cushy UI that Monte Carlo offers, which helps me see what tables are feeding into each other or what came beforehand. Review collected by and hosted on G2.com.

I'm often dealing with alert fatigue due to false alarms with the SQL monitors in Monte Carlo. I'm constantly checking on things that either self-resolve or don't need input, which is a bit of a hassle. It's mostly about configuring and tweaking the monitors to reduce the number of unnecessary alerts. Review collected by and hosted on G2.com.

What I like most is how Monte Carlo shifts data quality from reactive debugging to proactive observability. Instead of waiting for broken dashboards or stakeholder complaints, we can detect anomalies at the data level early - especially on partitioned, time-series datasets where issues surface quickly.

A few things stand out in practice:

The UI is nice and clear.

Pricing is reasonable, but the difference between the Scale and Enterprise tiers isn't clear.

The Monte Carlo support is quick and helpful. Most of the issues were solved within a few hours.

Anomaly detection that actually works in real workflows. The ability to monitor freshness, volume, and distribution changes across domains (Product, Finance, Business) helps us catch issues before they propagate into decision-making.

Scalability via monitors-as-code. Integrating Monte Carlo into CI/CD (GitHub Actions, domain-specific repos) makes data quality reproducible, reviewable, and scalable across teams - not dependent on manual setup in UI.

Cross-domain visibility. In a setup like ours (Trino + S3/Glue + ClickHouse), having a single place to surface incidents across domains is critical. It creates a shared language between Data Office and other teams. However, our tech stack is unusual for the platform.

Clear ownership model enablement. Monte Carlo supports the model we aim for: domain teams own their data quality, while a central team provides governance, standards, and observability. Alerts become actionable because they can be routed to the right owners.

Fast incident investigation. Even without perfect lineage everywhere, the context MC provides (upstream/downstream signals, history) significantly reduces time to understand “what broke and when.”

Pragmatic flexibility. It works across different stages of maturity - from quick anomaly detection to more structured, SLA-driven data quality processes.

If I had to summarize in one line:

Monte Carlo is most valuable not as a tool, but as the backbone for building a scalable data quality operating model. Review collected by and hosted on G2.com.

What I dislike most is that while Monte Carlo is strong as an observability layer, it still requires quite a bit of surrounding infrastructure and process to make it truly effective at scale.

In our setup, lineage is not equally mature across all engines. For example, with Trino and ClickHouse the visibility is limited compared to Databricks and Snowflake, which makes root cause analysis less reliable and often requires manual investigation.

There is also some integration friction. Certain systems require workarounds, like older ClickHouse versions or limitations in Tableau access control, which adds operational overhead and slows down adoption across domains.

Trino support isn't native. We use Starburst to make an integration.

Ownership and alert routing are not fully solved within the platform. Alerts are generated well, but assigning clear responsibility and ensuring follow-up still depends on external processes and team structure. Stronger built-in ownership and escalation mechanisms would help. Also, we use YouTrack as a bug-tracking system, which makes things less trackable for us.

From a usability perspective, managing a large number of monitors becomes harder over time. It is not always easy to understand monitoring coverage or to manage monitors at scale without relying on external tooling or code-based workflows.

The pricing model is another challenge. The credit-based approach can be difficult to predict and plan for, especially when scaling across multiple domains and teams. It requires continuous optimization and careful usage tracking.

Finally, while anomaly detection is strong, the higher-level intelligence is still evolving. It would be valuable to have more actionable insights, such as clearer grouping of incidents or better support for identifying likely root causes.

Overall, Monte Carlo is very good at detecting that something is wrong, but scaling the operational side of data quality still requires additional effort outside the platform. Review collected by and hosted on G2.com.

I really appreciate how easy Monte Carlo is to use, which makes identifying what's wrong with the data straightforward. I like that it provides a quick way to configure default anomaly detection on data assets at scale. The initial setup was very easy, and we were able to start monitoring about 80% of our assets right away. It's also great that Monte Carlo integrates with tools like Looker and PagerDuty. Review collected by and hosted on G2.com.

The way monitors are defined and changed (the migration that happened recently) is a bit confusing. The distinction between built-in monitor and custom ones was a bit difficult to understand for some consumers. Also, the 'forced' training of data for anomaly detection is tricky, as a lot of users ask how to better train the data that Monte Carlo has to tweak the detection. There should be a way to configure the thresholds before the actual datasets get trained properly. Review collected by and hosted on G2.com.

I like that Monte Carlo is integrated with AI, which I find really useful. It's great that it can automatically suggest adding tables, monitors, and setting alerts, plus recommending which alert tables might be missing. This AI-driven feature is very helpful to me. I also recently noticed the Agent preview feature, which allows me to ask simple questions in English, like about tables that are consuming more resources. This eliminates the need to manually query databases for these stats, improving our data warehouse efficiency through cost, read, and write optimizations. Additionally, I find Monte Carlo very user-friendly. Anyone can learn the features and explore them easily, typically within a couple of days. The documentation and videos are readily accessible, making the initial setup very straightforward. Review collected by and hosted on G2.com.

I see some features, maybe missing when working in a big query, like with projects on Google Cloud provider. I'd like Monte Carlo to have integration with Google buckets. It would be helpful if I could set alerts for files not landing on time or if empty files land in the bucket location. Currently, I have to use Python scripts to manage this, and if Monte Carlo had this feature directly, it would be very cool. I have a workaround by creating an external table on top of these buckets and adding it to the ingestion, but direct integration would be much better. Review collected by and hosted on G2.com.

I like the automatic thresholds in Monte Carlo's monitors, which makes it easier not to worry about setting dynamic or fixed thresholds thanks to the automatic ML threshold feature. I also appreciate its integration with orchestration tools like Airflow and DBT, as this allows us to check on specific failures in our workflows. These features help solve our observability issues related to data quality. Review collected by and hosted on G2.com.

Monte Carlo is a great tool but it is very overwhelming. Recently, there have been a lot of changes that affect our processes, like API endpoints, UI, contract, and monitor settings. These changes make us work too much, and they don't share these changes ahead of time. I also don't like that Monte Carlo doesn't allow running SQL queries if the table is not enabled for monitoring. There are some tables we need in queries but don't need the default monitors. The initial setup was quite easy 4 years ago, but now it's not that easy. Alerts are very noisy, and it would be helpful to have a dashboard view to manage these alerts. Review collected by and hosted on G2.com.