Monte Carlo Reviews & Product Details

I like how Monte Carlo is very user-friendly, which was a big draw for us. The pleasant user experience stands out, as they have really thought about everything regarding data quality and observability. Their hyper-focus on creating the best product for their customers is apparent, and they seem to be consistently evolving, especially with the new AI features available. These features have been helpful in making the process of creating monitors faster and smoother. I also appreciate their good customer service and the support provided, which was very good for onboarding. Review collected by and hosted on G2.com.

Certain lineage aspects of Monte Carlo could be improved if we were able to dive deeper into the field level view. Also, setting up Monte Carlo seemed a little more difficult than described, though a lot of that was due to internal security reviews rather than Monte Carlo itself. Review collected by and hosted on G2.com.

I use Monte Carlo to validate data. With large amounts of data, it can isolate the high-sensitivity cases I need to address. I like that the application is user-friendly and looks nice to use. The SQL query portion is easy to use and self-explanatory for someone with a SQL background. I can query for the validations I’m looking for and adjust the rules to my liking. The monitors show exceptions, alerts, and emails, and give me everything I need to succeed. I also wanted a centralized application instead of multiple internal proprietary applications. Review collected by and hosted on G2.com.

I wish Monte Carlo could send exceptions directly to certain people with a comment. Right now, I have to export them to Excel, put them in an email, and send them out. The initial setup was difficult because Monte Carlo was a brand-new application. Review collected by and hosted on G2.com.

I like that Monte Carlo reliably runs a pretty simple task and helps us feel confident that certain bugs don’t exist in our code. I value the custom SQL monitors we use for that. Review collected by and hosted on G2.com.

I haven't gotten much value out of Monte Carlo's AI features. They could be useful if they had more context from a broader AI system, since the system can't know what's going on from a single query. We're only hooked up to Snowflake, so the performance monitoring features aren't very useful for us. Review collected by and hosted on G2.com.

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 combination of automated anomaly detection and end-to-end data lineage has been fantastic for us. It proactively alerts us when data is missing or looks anomalous, which has significantly reduced our overall data downtime and strengthened the organization’s trust in our analytics. Review collected by and hosted on G2.com.

Everything has been great so far. I don't have any negative feedback at this time, but I'll update my review if I run into any issues. 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.

Monte Carlo monitors our Redshift warehouse with almost no setup. The automatic table monitors catch freshness, volume, and schema changes across our Kafka and ODS tables, so the Data Engineering team can hear about a broken pipeline before the analysts do. Alerts route to Slack and PagerDuty, which fits cleanly into our on-call rotation. Other teams (Search, Ads, Tracking) can also build their own metric monitors and custom SQL monitors on the same platform, so data quality checks aren’t all on our team. I also like the MCP server: from Claude Code, I can triage an alert, check lineage, and review the monitors without leaving the terminal. Review collected by and hosted on G2.com.

Some monitors can get noisy, and tuning them still takes a lot of manual effort. For example, one custom SQL monitor on our tracking events triggered 36 incidents in 30 days, and the team has to keep adjusting thresholds by hand to reduce alert fatigue. Metric monitors on our larger Redshift tables also sometimes time out or fail with errors, and it isn’t always obvious from the UI what caused the failure. It’s also easy to end up with monitors that effectively check nothing. A few of ours still point to tables that no longer exist and show “0 tables,” but there’s no warning to the owner. On top of that, many monitors don’t have a notification channel configured, so an anomaly can sit unnoticed. Better default settings for routing and some kind of cleanup or guardrails would help a lot. Review collected by and hosted on G2.com.

It is very helpful to control schema changes or even large additions or deletions. Monitors with AI are so intelligent and provide confidence on "if something happens, I'll be notified". If you configure it properly, you can sleep well :)

The UI is super intuitive and easy to set. You can also link it with pager duty to trigger alarms so it is a good quality advisor. Review collected by and hosted on G2.com.

The only thing that I can dislike a little bit is how verbose Monte Carlo is if you configure too much things. If you have a big DWH with hundreds of tables, and you configure hundreds of monitors... the alert channel in slack could be a mess. But it depends more on how good you are setting the correct and needed monitors. Review collected by and hosted on G2.com.

I love the monitors-as-code feature, since it lets us keep our monitors directly in our codebase. The integrations with the data warehouses and platforms we already use are also stellar. Review collected by and hosted on G2.com.

Ironically, the main pain point for me is the monitors-as-code data structure. It was recently revamped, and the new version is definitely clearer, but the overall structure still feels a bit unintuitive, and the documentation can be lacking at times.

Another issue for us is that we can’t define cron schedules for certain monitors. That makes it problematic to monitor our pipelines that themselves run on cron jobs. I understand Monte Carlo prioritizes and pushes the auto-ml / AI monitors, but sometimes simpler monitors that run on exact schedules are simpler and, for our use case, superior—which is what we prefer. Review collected by and hosted on G2.com.

I like that Monte Carlo is simple to use and easy to integrate. We gave it to developers with very little training, and they were able to instrument monitors quickly. It has a wide range of connectors for multiple data sources, and it’s simple for different data teams and owners to create monitors on the assets they own. I can identify anomalies and act on them before customers see them. Review collected by and hosted on G2.com.

I find the pricing strategy cumbersome and very difficult to predict. I have no idea how much it will cost when someone uses the troubleshooting agent to explore an alert, and I can’t predict what a monitor will cost. It’s very difficult to manage and control these costs. The default settings do not protect me from unexpected costs. For example, the default of deploying a table monitor on ALL domain assets results in massive, unintended costs. Review collected by and hosted on G2.com.