Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
data engineer
What do you like best about the product?
the fact that 100% of my tables are monitored, that all thresholds can be dynamically configured by the ML, and the UI is super easy to use it makes debugging easy
What do you dislike about the product?
- no slack owner assignments
- queries that are sent to Snowflake are not optimized
- no monitoring on read query performance
0 lineage is too much, and hard to navigate and filter out assets, and when I filtered out assets, except that nothing would be there, and the screen would adjust
- queries that are sent to Snowflake are not optimized
- no monitoring on read query performance
0 lineage is too much, and hard to navigate and filter out assets, and when I filtered out assets, except that nothing would be there, and the screen would adjust
What problems is the product solving and how is that benefiting you?
monitoring all data
- Leave a Comment |
- Mark review as helpful
Monte Carlo provide reliable and accurate data observability to our data stack.
What do you like best about the product?
I like the most about Monte Carlo is the Automated Monitoring functionality. Because it remove the hassles of need to create monitor for each tables, by automatically applied the Freshness, Volume and Schema change monitor to any new table imported to our database.
What do you dislike about the product?
Most dislike is its UI. I feel that the UI is not inituitive. Eg;
What problems is the product solving and how is that benefiting you?
Monte Carlo help to automates thousand of tables in our databases. It provide a consistent observability and come with multiple monitoring option. Plus we can integrate Monte Carlo to our Slack channel to provide alert to our team. With Monte Carlo, we dont need manually create a custom SQL script for our tables, as Monte Carlo helps to automate those task
Very easy to onboard with an excellent team that tailors their work to our success
What do you like best about the product?
Monte Carlo is very easy to use and connecting it to our stack was fairly simple. The documentation on their university allowed us to operate at scale, we only needed core employees to have access to live sessions and they quickly got up to speed to train others.
The fact that we can get immediate support using slack, email or any other channel, with instant feedback, gave us that extra reassurance that we were going to be well cared.
On top of that, Monte Carlo has a lot of monitoring features that make our life easier and point us in the right direction in the journey of improving our data observability experience.
The fact that we can get immediate support using slack, email or any other channel, with instant feedback, gave us that extra reassurance that we were going to be well cared.
On top of that, Monte Carlo has a lot of monitoring features that make our life easier and point us in the right direction in the journey of improving our data observability experience.
What do you dislike about the product?
The fact that we can create monitors "as code" / via API is awesome, but they are not compatible with the visual configuration interface, meaning that we are not able to automate the release of new tables with automatic monitors and, at the same time, allow less technical people to tune the monitors from an easier interface. This is not a deal breaker and is definitely in their long term roadmap, but not release yet
What problems is the product solving and how is that benefiting you?
Decrease SLA for MTRR (time to detect and fix) for data problems in production
Improve the data trustworthiness with data product owners
Scale the number of data products without increasing the number of people to upkeep them
Improve the data trustworthiness with data product owners
Scale the number of data products without increasing the number of people to upkeep them
Great onboarding processes, fast communication, continues development - new features each month
What do you like best about the product?
Monte Carlo enabled us to quickly integrate data quality into our data pipelines. Their onboarding process was briliant and helped us alot in understanding of data quality issues. Additionaly their platform is very mature in features and while providing great UI it also provides API's that can be used to incorporate those features programmatically.
What do you dislike about the product?
Lack of terraform provider to enable Infrastructure as a Code integration.
API limits are very low but can extended by contacting customer support.
Missing clean and concise tracking of raised issues and requested features.
API limits are very low but can extended by contacting customer support.
Missing clean and concise tracking of raised issues and requested features.
What problems is the product solving and how is that benefiting you?
Data quality in data pipelines. Data lineage. Notification framework enabling fast and reliable information directly to the data producers/consumers/stakeholders.
Easy to use observability tool
What do you like best about the product?
Non technical people can start using it with just basic sql knowledge.
What do you dislike about the product?
The commercial model that pushes you to pay for assets you do not necessarily want to track.
What problems is the product solving and how is that benefiting you?
It allows you to track your data assests with very low effort.
Administering the MonteCarlo tool in a Pharmaceutical company
What do you like best about the product?
- customer support is highly responsive, active and eager to help
- programmatic resources like Monitors as Code, API that enable plugging MonteCarlo in CI/CD pipelines
- graphical representation of incidents, data flows and patterns
- data products feature
- programmatic resources like Monitors as Code, API that enable plugging MonteCarlo in CI/CD pipelines
- graphical representation of incidents, data flows and patterns
- data products feature
What do you dislike about the product?
- documentation on the API usage around getting the results of monitors, triggering the monitors programmatically could have more examples
What problems is the product solving and how is that benefiting you?
Team that I work with is able to easily apply the data quality metrics and spot the data anomalies or data flow incosistencies way easier than before.
Great solution for data observability
What do you like best about the product?
- The tool overall works great. Offered features are enough to cover wide spread of use-cases.
- The team is also great. We've always had very quick response to our support requests.
- Automation features are the best. We've set up almost everything using code, which makes resources easily manageable.
- They are very open for feature requests and deliver them relatively quickly. We requested monitoring support nested fields and structs, which was implemented within weeks.
- The team is also great. We've always had very quick response to our support requests.
- Automation features are the best. We've set up almost everything using code, which makes resources easily manageable.
- They are very open for feature requests and deliver them relatively quickly. We requested monitoring support nested fields and structs, which was implemented within weeks.
What do you dislike about the product?
- We had some headache during Databricks integration, which was mostly caused by our platform not being Unity enabled yet. But with support, we've dealt with all the issues.
- There is a blocklist feature which works on schema level. It would be great if we could block table level access with that feature.
- There is a blocklist feature which works on schema level. It would be great if we could block table level access with that feature.
What problems is the product solving and how is that benefiting you?
We're leveraging its anomaly detection capabilities to great extend. Almost all our pipelines and tables are monitored for various use-cases. It works much better than some alternatives we've used.
Best Data Observability Platform
What do you like best about the product?
i like the way how MonteCarlo provides standard out-of-the box monitors, simple -no frills - UI to setup, the way how monitors, alerts are integrated with Slack, Collaboration from Product team on day to day basis in slack, promptness in response, knowledgable product managers & periodic sync up with them, Incident management, data sharing
What do you dislike about the product?
There is a period initially when we got bogged down by alert fatigue & few monitor setup options that were maturing. Those have been eliminated as of now
What problems is the product solving and how is that benefiting you?
near real-time Data Quality checks on the data, immediate alerting mechanisms in Colloboration channel, ability to create domains & have business users self-service - without losing the overall observability & control on the environment.
Great tool for Data Governance with space for improvements
What do you like best about the product?
I really like the integration with airflow, allowing to identify tasks that load specific tables.
The monitors are also very useful and the possibility of identifying domains and personalize the alerts for each of them.
The customer support is really good and fast.
The monitors are also very useful and the possibility of identifying domains and personalize the alerts for each of them.
The customer support is really good and fast.
What do you dislike about the product?
I am not so confident about the field lineage, specially when copying data, we have faced sometimes the disruption of the lineage due to that.
What problems is the product solving and how is that benefiting you?
Is spotting any issue with data really fast allowing us to fix some problems before business even noticing that.
Great combination of data observability and data quality
What do you like best about the product?
1. the ease of setting up and understanding the monitors
2. Great variety of audiences and the ability to configure custom messages that includes elements from your actual query
3. The observability part is extremely powerfull. It observed all irregularities that were reported by users in ServiceNow plus an additional set of findings
4. It's good to see that Monte Carlo develops in an iterative way. You see the application continously changing, mostly for the better while the basic functionality stays in plays.
2. Great variety of audiences and the ability to configure custom messages that includes elements from your actual query
3. The observability part is extremely powerfull. It observed all irregularities that were reported by users in ServiceNow plus an additional set of findings
4. It's good to see that Monte Carlo develops in an iterative way. You see the application continously changing, mostly for the better while the basic functionality stays in plays.
What do you dislike about the product?
Monte Carlo is not yet really suited to work with many from multiple teams. People from different teams can see and report on each others monitors, which is good, but it's hard to create with one mouse click an overview of all monitors and incidents for which a particular team is responsible for. We misuse a combination of domain and audience to achieve this plus I appointed myself as Monte Carlo data steward to enforce that users stick to a naming convention for monitors and dashboards
What problems is the product solving and how is that benefiting you?
1. Providing a stable, easy to maintain platform to store and run SQL business rules that have been defined by data stewards working in staff departments in our organization. We report the data quality in a Qlik dashboard
2. Perform pro-active data observability where we want to move away from a situation where our data users report about data issues to a situation where we can pro-actively inform our data users about data issues
2. Perform pro-active data observability where we want to move away from a situation where our data users report about data issues to a situation where we can pro-actively inform our data users about data issues
showing 61 - 70