Monte Carlo Reviews & Product Details

The built-in machine learning monitors that track freshness, volume, and schema changes are fantastic. I really appreciate how these features work right out of the box. Review collected by and hosted on G2.com.

To be completely honest, this is the best tool I have used for data observability and large-scale data quality checks. However, if I had to mention one drawback, it would be the extra features that come with the integrations. For example, MC attempts to display traces from our Airflow integration in several areas, but I have noticed that the information is not always accurate in some places. I have observed a similar issue with the dbt integration as well. Review collected by and hosted on G2.com.

I've found field lineage to be far more useful than I originally imagined. The table importance scale is also very nice to see. It has allowed us to get ahead of data quality alerts before our stakeholders are even aware of anything wrong. I find it easy to navigate especially and track down the most important models. There is a feature that let's you know if a query has changed based on the number of characters in a query, which is really nice. Review collected by and hosted on G2.com.

I really wish there was a way to snooze the monitors and alerts in the same manner, as it can sometimes become overwhelming. Review collected by and hosted on G2.com.

Monte Carlo has allowed us to monitor our data pipelines with increased clarity. One of its standout features is its ability to catch errors before they reach production, significantly reducing downtime and ensuring data integrity.

This product also played a crucial role in supporting our new client-facing data product. Its robust error detection and comprehensive reporting capabilities enabled us to launch with confidence, knowing that our data was accurate and reliable. Review collected by and hosted on G2.com.

The learning curve for setting up monitors, and understanding the system, was steeper than expected. Combined with the large number of tables in our warehouse, it was a laborious implementation process. Some of these issues are unavoidable. In the future I'm curious if there's a more efficient way to set up monitors. For example, in our case we set up the exact same rules for multiple tables, with the only difference being the field name and some slight variations in the SQL. Review collected by and hosted on G2.com.

I like how Monte Carlo brings data quality insights to the people who can fix them, the users of the data sources. I also find the ML thresholds helpful because they let Monte Carlo handle the error alerts, so the data platform team doesn't have to create the error thresholds manually. The integration with Slack is another plus, as it offers a centralized place for alerts and makes it easy to send them to the right stakeholders. Monte Carlo is easy to use, even though I didn't handle the initial setup. Review collected by and hosted on G2.com.

I'm having challenges with integrating Monte Carlo with AI agents. It would be great if AI agents could interact more seamlessly with Monte Carlo. Review collected by and hosted on G2.com.

I like Monte Carlo for its AI features that automatically handle the creation of boundaries when you select a source to be monitored. The automatic monitoring of schema changes, metric changes, and freshness is also great. I appreciate its integration with Slack, enabling the creation of automated workflows and keeping everyone informed proactively. The AI feature and automatic monitoring save a lot of time by eliminating the need to manually think about boundaries or constantly check for schema changes. Setting up the system was very easy, as all systems were connected quickly through admin accounts, taking less than a day. Review collected by and hosted on G2.com.

The main thing I don't like about Monte Carlo is how you need to select tables. We're really careful about what tables and sources we want to monitor, and that takes quite a lot of time. It's not super easy to navigate and select or deselect tables from a schema. That could be improved in my opinion. Review collected by and hosted on G2.com.

I use Monte Carlo mainly for monitoring data quality and reliability across our data pipelines. I like that it helps us quickly detect anomalies, broken tables, or unexpected changes before they impact downstream analytics. I really appreciate the automated data monitoring and alerting—it surfaces issues without requiring constant manual checks. The visibility into data lineage and pipeline health makes debugging much faster. It integrates smoothly with existing data tools, making adoption easier for the team. The automated monitoring and alerting help me catch data anomalies quickly, fixing issues before they affect dashboards or business decisions. The data lineage feature is especially valuable because it shows how datasets are connected, making it easier to trace the root cause of a problem. Together, these features save a lot of troubleshooting time and improve overall confidence in our data. Review collected by and hosted on G2.com.

Sometimes the alerts can feel a bit noisy, especially when multiple related issues trigger at once, so better alert tuning or grouping would help. The initial setup and configuration also took some time to fully understand. Improving customization and making onboarding a bit more intuitive would make the experience even smoother. Review collected by and hosted on G2.com.

The flexibility and getting timely and reliable alerts for Volume, Schema and Freshness is useful. Able to tune the model is great. Review collected by and hosted on G2.com.

Not dislike, but couple of things that can be better:

1) Dashboards can be better in providing more actionable insights like most frequently failing tables or top 5 failing tables, under which schema, failing for what reason, frequently failing monitors, etc

2) It would be great if any updates made on alerts in Monte Carlo can flow into ServiceNow incidents

3) Additional integrations with files would be great, like if a file has not arrived, etc.

4) If we can have the model tuned for alerts much sooner than 2 weeks would be a welcome move.

5) Conducting any workshops on a sandbox environment for teams would help engage more teammates to understand and gets on with Monte Carlo Review collected by and hosted on G2.com.

The way Monte Carlo surfaces anomalies in data freshness and pipeline behaviour is extremely helpful. It lets our team catch quality issues before they impact downstream users. The custom SQL query alerts are very accurate, and they save me a lot of time by pointing me straight to where things are breaking. Review collected by and hosted on G2.com.

The email alert formatting is restrictive — it’s difficult to insert clean tables or richer layouts for downstream users. More Outlook‑style formatting support would be a big improvement Review collected by and hosted on G2.com.

I really appreciate the monitoring feature in Monte Carlo. It's great because we can write custom alerts and emails that are integrated with Teams, making it really easy to keep our stakeholders informed about any data quality issues or key updates they're looking for. It's really powerful for understanding exceptions in the data, even those that aren't directly failures or major data quality issues, which our team finds very valuable. Review collected by and hosted on G2.com.

It would be great to integrate the alerts and monitoring section more closely. Some of the UI elements could do with improvements. The standard parts in the emails could be adjusted since they always indicate pipeline failure or warning, but sometimes they are just informational. I also wish it could be integrated closer to our data to avoid repeating the same code in various places. Review collected by and hosted on G2.com.

I like the Slack integration of Monte Carlo, where we get alerted through Slack, which acts as a one-stop shop for checking all the issues. This integration saves a lot of time. The initial setup wasn't that difficult because a Monte Carlo rep walked us through the process and provided a detailed knowledge transfer on how best to use the tool. Review collected by and hosted on G2.com.

Some of the rules are too sensitive, triggering a lot of alerts where we end up taking no action at all. There is room for improvement here. Maybe there should be a correlation between different table alerts, so if there are similar columns in other tables, then their rules should be imported; rather than training the new alert freshly each time. Review collected by and hosted on G2.com.