Monte Carlo Data + AI Observability Platform
Monte Carlo DataReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
485 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Great Anomaly Alerts, but a Verbose UI and Weak Monte Carlo as Code Docs
What do you like best about the product?
Out of the box functionality. Good alerting on anomalies, has caught many incidents over time.
What do you dislike about the product?
The UI is not user friendly and pretty verbose. The documentation on Monte Carlo as Code is really poor.
What problems is the product solving and how is that benefiting you?
Monte Carlo helps my team with alerts on data anomalies, primarily row volume anomalies. This has helped us identify multiple incidents.
Intuitive Data Observability
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
Monte Carlo helps notice missing or improper data. It's easy to use, integrates with tools like Slack and Jira, and has a user-friendly UI. Before we haven't had real monitoring, so it's a game changer for us
Enhanced Data Reliability with Powerful Monitoring
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
I use Monte Carlo to monitor data quality and reliability, catching anomalies early and reducing manual checks. It improves trust in our data, enhances visibility into data pipelines, and integrates with existing tools, which streamlines troubleshooting and response times.
Integrative Dashboards with Smooth Setup
What do you like best about the product?
I like Monte Carlo's integrations with SaaS products, especially with Databricks and Snowflake, which help us organize, predict, and respond effectively. The initial setup is good and straightforward.
What do you dislike about the product?
I find user management in Monte Carlo could be improved.
What problems is the product solving and how is that benefiting you?
Monte Carlo helps with governance and organizes, predicts, and responds effectively by integrating with SaaS products like Databricks and Snowflake.
Clear, Actionable Alerts That Catch Data Issues Early
What do you like best about the product?
What I like best about Monte Carlo is how good it is about catching data issues before they become real problems. The alerts are clear and actionable, which saves a lot of time. It’s given us much more confidence in the reliability of our dashboards and reports.
What do you dislike about the product?
I’d like to see deep-level support for Spark on Databricks, when it comes to capturing column-level lineage for some of our more complex transformation jobs. While the high-level lineage is good, getting that granular detail sometimes requires more manual configuration than I’d prefer for a tool.
What problems is the product solving and how is that benefiting you?
It solves the problem of unreliable data and the fire drills that come with broken dashboards or failed pipelines. Instead of reacting to issues after stakeholders notice them, we can proactively detect and address anomalies early, helping us deliver business critical dashboards more smoothly.
Makes Monitoring Our GCP Pipelines So Much Easier
What do you like best about the product?
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.
What do you dislike about the product?
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
What problems is the product solving and how is that benefiting you?
For me, the biggest value is the strong integration with Google Cloud. Monte Carlo picks up on freshness and pipeline issues across our GCP stack without any extra overhead. The custom SQL alerts are also a huge benefit — they let me monitor exactly what matters for our engineering datasets and surface issues in a very targeted way. Together, these help me identify problems early and keep downstream users informed
Powerful Monitoring, Complex Setup
What do you like best about the product?
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.
What do you dislike about the product?
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.
What problems is the product solving and how is that benefiting you?
I use Monte Carlo to expose DBT warnings and monitor trends over time, create custom rules for data alerts, and inform stakeholders of data quality issues through Teams integration.
Robust Data Quality with Some SQL Limitations
What do you like best about the product?
I like the ML-based anomaly detection and the ease of setting up data quality monitors in Monte Carlo. The web hook integration and data lineage features are valuable, especially for helping my data operations team troubleshoot issues by digging through data discrepancies. The process of setting it up was fairly straightforward.
What do you dislike about the product?
Column lineage is a bit limited with complex SQL and can be improved. An example is if there is a switch case where source data could be sourced based on condition, it is not yet supported.
What problems is the product solving and how is that benefiting you?
I use Monte Carlo for data observability and governance. It solves data quality, validation, and anomaly detection issues. The ML-based anomaly detection helps find unexpected data volumes, and data lineage aids in troubleshooting discrepancies by tracing data through its lifecycle.
Intuitive UI That Catches Issues Before They Hit the Pipeline
What do you like best about the product?
I really enjoy the intuitive UI. I also like that it helps catch issues early, before they make their way into the pipeline, which makes the overall process feel smoother.
What do you dislike about the product?
I do wish Monte Carlo were more “set and forget.” In the early phase, acknowledging incidents can take a while, especially with the number of monitors we’ve set up. I also wish there were a cooldown period after setting up a monitor in Monte Carlo, so the training data could keep learning until it’s truly “ready.”
What problems is the product solving and how is that benefiting you?
Identifying issues before it occurs. Seeing where the issue falls and speeding up my investigations help save my time.
Powerful what-if probability modeling, but results hinge on getting input distributions right
What do you like best about the product?
it transforms "what-if" scenarios into data-driven probability distributions, providing much more clarity than a single-point estimate ever could.
What do you dislike about the product?
The model is only as good as the probability distributions you feed it. If you choose the wrong input distribution (e.g., assuming a Normal distribution when the data is skewed), the results will be confidently misleading.
What problems is the product solving and how is that benefiting you?
I haven’t been using this as much
showing 1 - 10