Sign in Agent Mode
Categories
Your Saved List Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

5 Reasons You Shouldn't Get MonteCarlo for your Business

  • By Daniel L.
  • on 08/30/2024

What do you like best about the product?
You Should't Get MonteCarlo If....

1. You like waking up everyday not knowing whats broken in your data pipelines. You always wanted to tackle Data like the Wild West.

2. You'd rather write your own custom ML alerts for ALL your data warehouse rather than having an easy out-of-the-box auto-alerting solution. How else would you prove to your manager you're a 10x Engineer.

3. You believe having a data lineage app is for babies. Real data engineers have the entire lineage map in their heads written in SQL.

4. You don't like tracking data incidents. I get it, sweeping problems under the rug makes the bad feelings go away.

5. You think 3rd party integrations to apps like Slack, Airflow and Cloud Data Warehouses like Snowflake & BigQuery is overrated.
What do you dislike about the product?
Nothing to say that I dislike. Only a few items on my wishlist to for new features that would really help my org.
1. Integration with GCP Dataform
2. Greater Data Catalog abilities.
3. Custom API integrations to auto run workflows after a trigger.
What problems is the product solving and how is that benefiting you?
MonteCarlo's main benfit we felt immediately was it's automated monitoring of the tables & data assets.

Without having to set up a cusom alert for every single table, MonteCarlo automatically trains on a baseline for each table you give it access to.
It figures out expected update frequencies, row number changes, schema changes, field anomalies, etc.

Thanks to this, tables we forget to monitor are automatically tracked and alerted on when there is an issue or change.

We have important production tables that suddenly behave differently, and we are able to quickly track bugs and outages that were realted to the anomaly.