Monte Carlo Reviews

Monte Carlo is a data observability tool that can help track data volume changes and flag incidents if there is any unusual activity on a table, data models, or any jobs. For instance, if something unusual happens on an ETL job, it will raise an incident and send alerts via integrated platforms like Teams application and emails.

Monte Carlo also helps in monitoring applications like ServiceNow, Jira, and Snowflake by establishing connectivity with them. The solution is beneficial for various scenarios, such as when sudden deviations from normal data patterns occur. For instance, if a cloud data warehouse like Snowflake experiences an unexpected change, Monte Carlo flags incidents immediately. Its AI agent enhances troubleshooting by providing analytical insights. Besides, integrations with other applications, such as ServiceNow and Jira, ensure an end-to-end alerting mechanism.

On an account level, it builds monitoring capabilities across vast data sources. It also supports triggering alerts via ServiceNow by using webhooks, allowing associates to take immediate action. Recently, Monte Carlo introduced an AI agent to aid in troubleshooting, ensuring only main production layers are analyzed. This backend troubleshooting does not grant complete access to all layers but remains highly effective in problem-solving.

The most valuable aspect of Monte Carlo's observability feature is its automation of the monitoring processes, which eliminates the need for an individual to manually monitor numerous models or tables. It flags issues with precision and ensures proactive resolutions only on the affected components, thereby enhancing efficiency vastly.

Monte Carlo's scalable nature further bolsters its value proposition. Once integrations are established, future model updates are automatically captured without additional setup costs or actions. Given that the data platform's needs perpetually grow, Monte Carlo provides seamless adaptability.

The software manages data auditing and monitoring across platforms like Snowflake with its robust algorithms. By analyzing metadata over an extended period, Monte Carlo's flagging system, based on deviations from historical averages, ensures precise incident identification. Its ability to utilize custom monitors further extends its value, as users can implement logic-based rules and receive targeted alerts.

The introduction of a performance tab greatly aids optimization, visually displaying runtime graphs to identify model issues quickly. Monte Carlo's near perfection in accuracy ensures every flag corresponds to a genuine issue, attested by its consistent performance over time.

Monte Carlo's AI troubleshooting agent, which mimics human oversight through tiered analysis, provides ample support in incident resolution. This ensures incidents are well-documented, analyzed, and tackled despite limited access to all data layers.

While Monte Carlo frequently updates its UI platform, the changes might pose adaptation challenges for long-time users, as the continual evolution is not always intuitive. Additionally, occasional latency hampers efficient access during critical incidents, leading to potential misses of high-priority alerts.

In terms of data accessibility, granting read-level access to non-sensitive data layers would enhance insights for users significantly. Users currently experience limitations in data layer access, such as bronze and silver data layers containing essential business logics.

Sharing metadata with clients could bolster Monte Carlo's analytical capacity, allowing clients to draw deeper insights from shared data.

I have been using this solution for four years.

I have never noticed something which Monte Carlo flagged that was not relevant to the issue. The accuracy is 100% from what I have noticed. I have never noticed any issues where something is actually happening on a data warehouse, but Monte Carlo still flags it as an issue. I have not seen these kinds of scenarios with Monte Carlo while working. The accuracy is consistently 100%.

I can say Monte Carlo's scalability is at approximately 90%. Once we establish the integration in the future, we can enable an option to capture the future models. We do not need to work again and again. Once we establish the connectivity, we do not need to work on adding new tables. It should be a one-time effort. This approach is more scalable. Data platforms will not stop growing from their beginning state. They will always expand. Monte Carlo demonstrates scalability in adopting new models automatically, which should serve organizations well.

We have connected to Monte Carlo regarding a few things. When we are establishing any new connection and face any issues, we reach out to them for technical support.

The technical support is fine. They will respond within two to three hours, but the solution may take some time, ranging from 24 to 48 hours. Technical support is satisfactory from them. Even though the product application team is not that much larger, they are still giving better support.

When onboarding Monte Carlo, you can review the documentation for whatever source you want to connect from Monte Carlo. There you can find more use cases.

When I started working with Monte Carlo, I did not see as many features as currently exist. Previously, the product did not have troubleshooting agents. Also, when I started working, it did not have a performance tab. The performance tab shows performance in a graphical way, allowing me to easily review the model and check the average run time. If there is any unexpected spike that happens for a specific day, I can see that.

For technical support, I would give it eight out of ten. Currently, for my account, we are not giving all layers access to Monte Carlo. We are only giving access to the main golden layer. We are not giving access to the bronze layer and silver layer because they contain business logics.

I am not certain about billing information because that is at an account level, and clients would be aware of billing information rather than myself.

My overall rating for this product is eight out of ten.

My organization relies on Monte Carlo for data observability, such as whether tables were loaded on time and whether the load met expectations regarding volume. We also use it for observability into our data transformation pipelines. We use it to trigger alerts to our respective product and engineering teams if loads are delayed or the volume of loads does not meet expectations. In essence, we use Monte Carlo to gain observability into our data.

We have encountered scenarios where a particular data load would not have generated any alerts if Monte Carlo had not been in place, since the data load went through successfully. However, the volume of the data loads in that case was below the threshold volume that triggered a volume anomaly alert from Monte Carlo. We were able to go back, fix the data, and report it to the upstream source.

We also use Monte Carlo to catch long-running queries. We have monitors set up for that purpose as well. We have an in-house solution developed to catch long-running queries on Snowflake in real time, something that is not currently available in any other SaaS providers for Snowflake.

The volume monitors and the anomaly monitors regarding volume, freshness, and data consistency are the best features Monte Carlo offers in my experience. These are the best features because they help flag issues that are more abstract and difficult to measure. While a data load that did not happen is an easier thing to track, a data load that happened but the volume was not in a particular range is a very tricky metric to monitor. That is a great feature.

It is mostly a combination of volume, freshness, and consistency monitors that I find myself relying on the most. The specific monitors I use depend on the business and use case we are catering to, the tables, and the data involved. It is difficult to point out one monitor as the most useful, but we use all three of them in different combinations very extensively.

Monte Carlo has had a major impact on my organization in terms of data health for the downstreams and for all the engineering teams that depend on our data. We are now getting timely alerts around the quality of the data, the volume of the data, and the health of the data. We are able to get that visibility more granularly into every single table. We are able to draw the data lineage to understand failures faster. Overall, Monte Carlo has had a very positive impact in terms of having healthier data and being able to trace through the data lineage to understand where exactly in the data life cycle things are going wrong.

Monte Carlo needs to stop their reliance on AI, as it is not going well and is degrading the entire product. They need to find their way back, establish a product roadmap, and have real engineers work on improvements rather than heavily push AI down users' throats. They need to stop relying on AI as heavily as they have been doing, as this has really degraded the user experience. The overall direction they are taking with AI needs to be examined, as at some point it seems they have simply stopped making any improvements.

We have not used Monte Carlo's AI capabilities significantly. We primarily use it for investigating alerts from time to time. However, we do not use it extensively, so I do not think it is fair to comment comprehensively on it.

Their incident tracking and incident debugging bot is useful for new analysts who are starting onboard. It helps them debug incidents, get a clearer picture, and achieve a clear head start to reach the root of the problem faster. Regarding accuracy and reliability, I would rate it at eighty to eighty-five percent. Given the current inherent non-reliability of AI models, every single thing that Monte Carlo says needs to be validated.

I have been using Monte Carlo for the last three years.

Monte Carlo is a fairly stable product.

Monte Carlo is robust and scalable for our data needs. We have not encountered any issues or challenges with the scalable platform.

We did not previously use any other solutions.

Time has been saved in reporting errors, SLAs, and performing reloads because we have been able to catch data errors faster. We estimate approximately eight to ten percent time savings, but regarding money savings and fewer employees needed, I do not think we can achieve that.

We have seen a reduction of incidents in approximately seven to eight percent in production scenarios, which has definitely been positive. I recommend checking out Monte Carlo to see if it fits your data-related needs. Conduct a thorough proof of concept, review the licensing and contract agreements, and if it meets your requirements, proceed with it. I would rate this review at seven out of ten.

I work as a business analyst and I usually see data anomalies in our company's data set, and I also work a lot on Power BI reports to see our performance on the supplier side.

When we receive data from our suppliers to view their performance, sometimes the data is not complete or they are doing backfills of previous data, so we have established some rules in Monte Carlo to monitor these anomalies, and whenever we see something passing a preset limit, we receive an alert.

When I open Monte Carlo, I usually look at my dashboard to see how many alerts we have received in the last few days, but I usually check the alerts in the last month, and I see which rule has received the maximum amount of alerts; then I try to solve it first because the pattern is similar, and then I try to solve other alerts based on other rules.

In my team, it's me who handles those alerts, but we have another team who works on these alerts as well, although they are working on another kind of data set, but in the company, it's used by many people.

The best features of Monte Carlo for my work are the ability to see alerts clearly, how many alerts we have received on which rule and for which country, and there is a feature called investigation query inside Monte Carlo which shows a pre-done analysis, so you don't have to run an SQL query by yourself to do manual checks.

It gives a clear analysis in a large data set, which is very time-saving, so I don't have to run manual codes to verify the data, and it has helped me a lot in saving time and improving efficiency while doing data checks or verifying data. It's a really great tool to explain the anomalies when we see one in Monte Carlo, as we have actual proofs to show to people or to the managers that we are having this anomaly or that data is missing.

There's also an AI feature that is inbuilt in Monte Carlo, but you have to pay separately for that feature, and I used it for quite a while in the beginning, but now my company has disabled it.

The biggest pain point with Monte Carlo is that we have created some rules, but those rules cannot judge everything, and I think the platform is a bit complex for someone new, so it can be more intuitive; a display adoption platform could guide the user on how to use this, like a DAP system. It took a lot of time for me to learn it, and without a guide, a new user would be clueless.

If I could change one thing about Monte Carlo, it would be for the platform to suggest some data quality rules by itself or some algorithms based on the anomalies and the patterns of our anomalies, which would be helpful, and also changes in our rules according to past anomaly patterns. I think that would be good, and they should also improve their support system, as I find it a bit weaker at the moment.

It's been six months since I've been working on Monte Carlo, and it's a really great tool for analyzing data quality anomalies.

Previously, the data checks were performed manually; they extracted data on Snowflake and then did manual verifications on Excel using formulas.

It was not me who implemented Monte Carlo; it was another senior data analyst who implemented it a year ago, but I think it took a few months to get everything up and running.

It needed formal training because the tool is not that easy; if someone doesn't have a data analyst or business analyst background, you have to explain every rule which you have set by yourself, because the rules are created by us, not Monte Carlo; Monte Carlo is just a tool. We put our own rules to govern the data sets, and we literally had to make a guide to help users get to know that platform.

It was not me who implemented Monte Carlo; it was another senior data analyst who implemented it a year ago, but I think it took a few months to get everything up and running.

Monte Carlo saves me roughly 30% to 40% of my time in doing verifications or data quality checks, and related to my team, I'm the only one who uses it in my team, but we collaborate with another team that uses it.

I didn't ask that question in my company; it was a good choice, so it's a very popular tool, which is why my company picked Monte Carlo.

I would like to leave a review for the tool called Monte Carlo, which is a data quality analysis tool.

I think they just changed the layout a little bit, and during my work, I didn't see any changes in the platform except for the AI feature, which I don't use anymore.

Our final goal is to automate every data quality manual check into Monte Carlo so we don't have to do a lot of checks by ourselves.

If I find something bizarre, I go to Monte Carlo and see if it's happening there as well, so it gives me confirmation that the issue is occurring and we can contact our supplier or the country to verify what it is.

Monte Carlo is a really good tool; whenever I do data verification checks for the dashboards, and if I find something bizarre, I go to Monte Carlo and see if it's happening there as well, so it gives me confirmation that the issue is occurring and we can contact our supplier or the country to verify what it is. I would rate this product a 7 overall.

Monte Carlo's main use case is setting rules to test the quality of data coming from the source side. For example, a rule can be set up for null checks in a particular column of source tables. If any condition is breached, I receive alerts, which is very helpful for providing quality data to my customers. Monte Carlo is also helpful in checking the freshness and volume of data. Freshness indicates whether data is coming from source sites at the correct frequency.

The feature I find myself using most is freshness. If the data is fresh and up-to-date, I can give the desired results to meet my business needs. However, if I have stale data that is not useful for the current date, then there is no point in working with it. Freshness is really helpful for providing up-to-date results or a clear picture to my business leads.

The best features Monte Carlo offers are that it can be used through the UI as well as creating monitors with the help of YAML. It is quite easy to create monitors using the UI, and I can find out the data freshness with the help of charts. This provides a quick and accurate review of my product.

Monte Carlo has positively impacted my organization by significantly reducing manual tasks. With alerts for any breaches of rules, I am easily and quickly notified, which is very useful and accurate.

One way Monte Carlo can be improved is when rules are breached, it sends an email containing alerts. However, if I want to analyze a particular alert deeper, I have to click on the alert link and further investigate in Monte Carlo's monitor UI. It would be beneficial to include a snapshot of the specific table or error in the alert email for better clarity.

There is also an issue with deleting monitors. If my schema or database is active, I can easily delete monitors, but it is quite difficult to remove monitors if the schema no longer exists. I had to use CLI for this use case, but I struggled a lot, so I request that Monte Carlo include this feature in the UI as well for easier deletion.

Regarding the features, I can mention that Monte Carlo has just updated the UI. The previous one was user-friendly, and now they have added AI-related elements in the current UI, which is good. However, I still struggle a bit to find things in the current UI, so they can improve that aspect further.

I have been used Monte Carlo for the last three years.

Monte Carlo is stable.

Monte Carlo's scalability is impressive. I can create multiple monitors on my data resources and for specific data products. It allows me to create many YAML files or numerous monitors within a single YAML file, making it quite scalable.

Customer support is quite good. When I requested help regarding the deletion of monitors, I received a very good and quick response. I give customer support a rating of ten out of ten.

I have only used Monte Carlo and did not previously use a different solution.

I have seen a return on investment with Monte Carlo. It definitely reduces resource hours needed for work, lessening the effort required significantly compared to when Monte Carlo is not in place.

My advice for others looking to use Monte Carlo is to definitely go for it because it is quite useful, accurate, and saves a significant number of hours.

Regarding Monte Carlo's AI capabilities, I am not sure about governance and security, but I find it very helpful for data observability. When linked with Collibra and Immuta, it indirectly contributes to data governance and security.

Monte Carlo is deployed in my organization on the public cloud.

Regarding Monte Carlo, people are not very aware of it compared to other capabilities, so I think they can work on improving their advertising efforts. I rate this review nine out of ten.

My main use case for Monte Carlo is data monitoring, monitoring jobs that have failed, and I have also used testing fairly extensively. I usually use the pre-boxed testing that Monte Carlo offers, but on a couple of other use cases I have developed custom testing as well.

I cannot remember the exact details of how I use custom tests in Monte Carlo because the last time I did it was probably several years ago. I think that it was generally testing that was not more generic, such as uniqueness testing or volume monitoring, but I honestly do not know if I can remember or give the exact details of what I was doing.

As far as doing anything very unique or different that I have tried in Monte Carlo, I would say I am more of a standard user of it. We have it connected to one of our Slack channels that monitors our jobs and any anomalies that we have within our data products. I primarily use it to keep an eye on some of my models that I am responsible for.

I have found a lot of value in volume anomalies with Monte Carlo. I do not remember what it is called exactly, but I have really appreciated that feature because it helps identify potential issues that might be hard to identify otherwise, such as if the data source has changed without my awareness, even though the schema did not change. Monte Carlo can still detect something that changed upstream and is not as obvious. Things such as that have been very helpful with any kind of volume anomaly detection.

As far as the volume anomaly detection in Monte Carlo, this is something fairly recent. I helped develop brand new models for our Genesis phone call system data. Something had changed upstream where some of the API calls were doing something a little differently. There was no schema change, but the volume increased dramatically overnight, which prompted discussions with the upstream data warehouse team to identify what those changes were so we could accommodate them in the analytics layer.

I think improved reliability with Monte Carlo has been valuable. Our team monitors the channel that feeds us any alerts on our models that we are responsible for. While we have not gone through every single alert yet, it has been very helpful for each of us to keep an eye on the models that we personally are responsible for. The alerting has been great, as well as some of the metrics, such as being able to identify tests that are failing. It has been helpful to identify those immediately rather than having to dig into the data and take the time to do the data discovery to find out what issues there are.

Having used Metaplane and Elementary and worked with those other tools, I think Monte Carlo had a gap or something that was not as strong, specifically around custom feature development. I mentioned that I could not give specific examples, and I do not think I could do that now, but Metaplane specifically had a strong area with that. Additionally, the UI in Monte Carlo can be a little overwhelming sometimes. That is another thing to add to my comments, but overall, I think it is fairly easy to use.

I think that all those areas in Monte Carlo, the specific examples mentioned such as documentation, have been fine, as well as the support as far as I know. I have not had to work specifically with issues regarding support. I have not had to work hard with the product itself as far as getting support, but overall it has been good. I have been able to find help with issues in the past through the developer documentation. For me, the only thing that feels a little overwhelming when using Monte Carlo is the AI, which is something I appreciated about Metaplane because it felt more user-friendly and did not feel so overwhelming.

I have been using Monte Carlo for probably three to four years collectively. I am using it currently at HubSpot and I have used it at two other previous positions.

We have tried different tooling, and I was part of POC work for trying out different tools such as Elementary and other related tools. We found that Monte Carlo ended up being the best for us because it was able to do pretty much everything that the other competing tools were able to do for us, as well as being pretty entrenched already in our data architecture. Another reason I think we ended up staying, which I think says a lot about Monte Carlo in general, is that they were able to work with us on pricing and assure that we were happy customers. As a large organization, we were pretty happy with the pricing and the negotiation that Monte Carlo was willing to do.

I would probably give Monte Carlo an eight out of 10. I think it is very usable and beneficial overall for data monitoring. I really appreciate things such as the time since last update, which is easy to find, row count changes, and even some of the orchestration, such as execution time, which has been really cool. There are some really cool monitors that come out of the box. Monte Carlo has some other cool things such as field lineage and table lineage that have been pretty cool to use. I can use it right within that tool and do not have to go to Atlan to look at that. Setting up personal dashboards has been probably a little harder to do compared to Metaplane or Elementary, but at least the functionality is there. That is kind of the reason I would give Monte Carlo an eight out of 10.

I think Monte Carlo's AI capabilities are fine overall. Monte Carlo seems to be doing what it needs to be doing as far as keeping the data secure in its product, even when using AI. I do not have much to say about that.

I personally have not used the AI tool within Monte Carlo much, so I probably cannot say I have a definitive opinion on that. I believe I might have used it once in the past and it helped me figure out what I needed to know as far as using some of the tooling in it, but I do not remember what I was trying to use at the time.

The first thing I would suggest to somebody brand new to Monte Carlo is to spend the time understanding monitors in general. That is for me the bread and butter of what the tool can do. I would suggest spending time in the developer documentation, understanding what each monitor does, some of the out of the box monitors such as volume testing, row count changes, and similar things. I think utilizing some of the custom fields or custom testing is really powerful if you know what you are doing and know how to implement that in a smart way. While the capability is there, I would suggest people really understand those two things specifically.

I would recommend Monte Carlo overall. I gave it an eight out of 10 because I think it does its job in helping us monitor our data products and making sure that nothing is breaking that we are not aware of, as well as being actively aware of any anomalies that might exist.

My main use case for Monte Carlo starts with working on data quality related problems, but now it is a very necessary element for our whole data pipeline because it lets us know about the freshness and other data quality related metrics as well, covering all the data quality related metrics, including completeness, correctness, accuracy, and majorly, the freshness part of it.

A specific example of how Monte Carlo helped me with a data quality issue is in our architecture, where we are getting all the data, storing all the historical snapshots in a raw layer, deduplicating it in the second layer, and curating it in the third layer, with alerts and monitors on all layers whenever we move from raw to dedupe or dedupe to curated, checking whether the number of IDs or the number of data is as expected or not, leading to alerts being triggered in the past for the orders table that helped us investigate pipeline related failures.

I often rely on Monte Carlo for our tables that get refreshed in three hours, where it sets up alarms or alerts if the tables do not get updated on their usual trend, such as triggering an alert if a table has not been updated for four or five hours.

Monte Carlo has positively impacted my organization by removing the need for manual monitoring of pipelines, automatically triggering alarms whenever something goes wrong, thus allowing the data engineering team to focus on more positive work, and helping us in manual tasks where after every logic change, we can track data and updates, along with proper catalog maintenance to find out specific information in our data warehouse.

Since using Monte Carlo, the freshness of our data has improved a lot from less than eighty percent to above ninety percent and there has been significant time saved, noting that while we do not keep a precise record of this, there is a steep decrease in time consumed on monitoring and related activities.

The best features Monte Carlo offers include an AI related trend analysis tool that checks the number of records of a certain table or the kinds of records affected by delete, insert, or update operations, triggering alerts if those numbers become unusual and providing a triage solution to investigate specific base tables or parent tables behind specific issues.

The AI trend analysis and triage solution have helped my team by alerting us during manual deletions or update activities and if there is a logic change in the main curated layer; if deletion rates deviate from expected numbers, we receive alerts that we may have messed up with the code, allowing us to check the code logics that we have implemented.

Regarding Monte Carlo's AI capabilities, it offers a tool that provides a mechanism to select or exclude specific parts of the data from the training cycle, allowing companies to adjust incorrect or ambiguous trends in the data, thus showing consideration for governance.

There are some improvements needed for Monte Carlo's code used for migration, which has not been set up well; improving documentation and migration features from other services, along with enhancing historical maintenance and version control on Monte Carlo's code, would greatly help.

In some cases, with multiple tables, the UI sometimes crashes, but it is still the best I have seen so far, making it a great tool overall.

I have been using Monte Carlo in my previous organization for about one year, and here in my current organization, I have been using it for one and a half years.

Monte Carlo is stable, with ongoing feature improvements; while there were initial breaking issues, they are fixed quickly when reported.

In terms of scalability, Monte Carlo handles our organization's multitude of tables and connections well, although there could be improvements in its implementation scalability, particularly with monitors as code.

Customer support was great, with dedicated resources from the Monte Carlo team who assisted with issues during our weekly calls, ensuring we understood specific features.

We previously used the Great Expectations library, which did not offer a solution like AI trend analysis and only provided basic data-based monitoring, lacking features that led us to switch to Monte Carlo.

In the beginning, I found that Monte Carlo took time to learn and understand the metrics and trends we have, but after six or seven months, it has shown great and accurate responses.

We have been tracking our return on investment, which has not been long, but we have saved significantly in time utilization of our resources and in capturing criticalities through this solution.

In terms of pricing, setup cost, and licensing, I rate it a bit high on the pricing side; it is pricey, but given the features and flexibility it offers during implementation, it stands out against specific libraries that are less handy to use, requiring extensive documentation.

Before choosing Monte Carlo, we evaluated Evidently AI, and our existing organizational ties to Monte Carlo influenced our decision-making.

My advice for others considering Monte Carlo is to assess whether their data platform is large enough to benefit from AI capabilities, as smaller scale industries with basic rule-based monitoring might find it a bit pricey. I would rate this review a nine out of ten.

My use case for Monte Carlo is both data quality and observability. We are using it as part of robustly monitoring the jobs as well as finding out any anomalies with respect to data quality issues.

In Monte Carlo, as part of observability, we have dynamic alert systems that learn the previous patterns of data anomalies and customize the monitoring system. It does not only have static rules because it has machine learning based models that learn the patterns. For example, during Thanksgiving, more purchases are happening, so you can expect more issues. It learns those patterns and sends the alerts based on that. The system does not send false alerts.

We use anomaly detection as part of a monitoring system. For instance, I was working for an airline where daily check-ins, checkouts, and transactions happen in real time. We wanted a very robust monitoring system that could monitor the data in real time. Whenever there is an anomaly, such as some columns which are not supposed to have nulls or which are not supposed to have certain data, you can train your machine learning model to have that threshold. You cannot just keep that threshold at 10% or something. You can train that machine learning model so that whenever a null detection happens or some kind of data mismatch happens, or when there is a schema change, it detects so many anomalies. We had many anomaly detection alerts.

The customizable alerts and dashboards in Monte Carlo were very customizable because it not only gives you the option to select alert features using drop downs, it also opens up a window where you can write your own customizable queries in SQL.

Certain features of Monte Carlo have contributed to maintaining our data trust by having multiple steps where you can define the model and also specify the probability distribution for your input. You can simulate that model over the past pattern. Additionally, it will give nice dashboards which are very handy and easy to understand to check how the anomaly patterns are progressing. If there is any sudden spike on a particular day, you can easily spot that and dig deep into it.

Regarding Monte Carlo, I would say that currently we can have machine learning options. We might have to integrate MCP servers so that it can connect to multiple systems at once and we should have some kind of a placeholder for artificial intelligence integration. Artificial intelligence can access multiple systems underneath Monte Carlo, such as any kind of database or any kind of real-time source systems. Currently, I think it is lacking that capability.

I have been using the solution since 2024, which is around more than two years.

The stability was very stable. I did not see any issues with respect to stability, and I would rate it a ten.

The scalability was good because when we enrolled it, it was already scaled up. We did not require it to be scaled up again, so I cannot fully comment on that.

I rate the technical support around nine out of ten because they are pretty responsive.

Data quality monitoring throughout the data lifecycle is very important, especially in this artificial intelligence era. If you feed garbage into artificial intelligence, it will hallucinate more and will not give you accurate results. It might divert into deploying many more agents and utilizing many more tokens rather than confining to a particular set of tokens. It is not only important from your data perspective, but also very important from your revenue perspective. The lost tokens are directly impacting an increase in costs or a decrease in revenue.

Regarding the pricing, it is a bit expensive compared to traditional monitoring systems provided by other vendors. However, the extra features and the trust come with some cost, so I think it should be fine. I have worked with many customers who do not have any complaints. In fact, they migrated many other systems from traditional monitoring systems to Monte Carlo. The customers are accepting of this pricing model.

Monte Carlo has many advantages compared to other solutions. As I mentioned, it has a lot of machine learning functionality and excellent user friendliness. The interface is quite crisp and the appearance is quite good. Traditional tools require some prior knowledge, but with Monte Carlo, you can onboard any user at any time. They can easily understand how to use that tool.

The solution requires maintenance because new features get rolled out and you need to upgrade those features. During that time there is a little bit of a pain point, but that is acceptable because you will experience new functionality.

If others are looking to implement this product, my advice is to robustly monitor their system with very little human intervention. Monte Carlo has an option where it will directly allow you to dig deep into the root cause and you just need to do a few clicks and it will get you to that data issue where it is happening. Very little human intervention is required for this. I give this solution an overall rating of eight out of ten.

My main use case for Monte Carlo is data observability.

To check if the ELT job fails is a quick, specific example of how I use Monte Carlo for data observability.

I use Monte Carlo to point out anomalies in data such as spikes or sudden drops in any particular data. We use Monte Carlo to observe all those things.

In my experience, I really appreciate Monte Carlo's automated anomaly detection feature. It is very helpful.

The automated anomaly detection in Monte Carlo helps me in my day-to-day work instead of doing everything manually.

Instead of writing rules manually, Monte Carlo learns users' behaviors and then automates data based on it, which is very useful for me.

The positive impact Monte Carlo has had on my organization is that it has accelerated the development process and has reduced the testing time significantly.

I can tell you that Monte Carlo has reduced testing time. If a particular project's testing alone takes 120 hours, it is reduced by three-fourths most of the time, which is extremely useful for us. It has impacted our numbers positively.

Monte Carlo can be improved further by having much more AI integrated into it. I can see that a more sophisticated way of doing things will be very useful.

The existing UI is pretty good, but it could be much more visual. The documentation is good as it is.

I have been using Monte Carlo for about two years.

In my experience, Monte Carlo is very stable.

Monte Carlo is quite scalable, and I am impressed by its scalability.

I would rate the customer support of Monte Carlo at eight or nine out of ten. They are quite good.

Monte Carlo was my first choice, and I did not use a different solution before it.

I cannot be very sure about money saved with Monte Carlo, but regarding time saved, definitely. We have saved more than three-fourths of the time in the testing phase.

I did not evaluate other options before choosing Monte Carlo. Monte Carlo was my first choice.

Regarding Monte Carlo's security features, it has pretty good security, and they are doing a good job on the security side of things.

Regarding Monte Carlo's AI capabilities, I would say its accuracy is around eight or nine out of ten.

My advice to others looking into using Monte Carlo is to learn everything first before using it, rather than testing everything as you go. I would rate this review seven out of ten.

My main use case for Monte Carlo is to create monitors to monitor data quality. I created different types of monitors, metrics, SQL, and custom SQL. I also utilize the Monte Carlo API to ingest data and create a datamart for analytical purposes.

Recently, I used the Monte Carlo API to ingest data to create a datamart, where I created several tables, such as the monitor snapshot, alerts, the run monitor history, and the monitor credit consumption.

Other use cases I have for Monte Carlo include creating a monitor, where I can write custom SQL to monitor data quality. If the data volume fluctuates dramatically, either increasing or decreasing too much, it will fire an alert.

Monte Carlo offers several great features that stand out to me. Monte Carlo's use of machine learning and AI to determine the threshold for the monitors that trigger alerts is particularly impressive.

Recently, Monte Carlo added features based on AI that respond to alerts. When you see an alert, the AI can help you analyze it and find the root cause.

Monte Carlo has positively impacted my organization by ensuring the data quality of the data pipeline, which is essential for data-driven decision-making. The company's business depends on data-driven decision-making, so data quality is very important. Monte Carlo monitors data quality issues and helps identify and fix those issues efficiently.

I estimate that I resolve data issues roughly 30% more efficiently since using Monte Carlo.

Monte Carlo adopted AI just recently, so there is room for improvement in the accuracy of the AI.

I have been using Monte Carlo for two years.

Monte Carlo is stable.

Monte Carlo's scalability is good. As our company's business grows and the data volume increases, Monte Carlo scales very well.

I find Monte Carlo's customer support to be good, and their customer support team responds very fast. We can submit a support ticket, and they also provide a platform using AI to answer questions. If the AI cannot resolve the issue, a ticket is created, and a team member will help.

I did not use a different solution before Monte Carlo.

My experience with pricing, setup costs, and licensing is limited as that falls under the management team's responsibility.

I am not responsible for how Monte Carlo is deployed in my organization. I believe the platform team is responsible for that.

I do not have a specific number regarding the return on investment with Monte Carlo, but I believe it saves a lot of workload for employees if we do not use it.

My experience with pricing, setup costs, and licensing is limited as that falls under the management team's responsibility.

I did not evaluate other options before choosing Monte Carlo. When I joined the company, we were already using it.

Monte Carlo does a good job overall. I rate Monte Carlo an 8 out of 10.

I chose eight because Monte Carlo does a good job, even though there are places for improvement. Overall, it is good.

Regarding Monte Carlo's AI capabilities, I find its accuracy and reliability of output to be good. Even though it is not 100% accurate, it is still good. A human review is necessary, but it does a good job.

My advice to others looking into using Monte Carlo is that it is a good product.

Overall, I think Monte Carlo is good, and the questions cover almost all the aspects. My overall review rating for Monte Carlo is 8.

Monte Carlo works as a centralized data tool. We use it for data observability and anomaly detection, which helps identify issues and changes in data flows.

The product allows us to segment data into domains and categories. It makes organizing work easier based on its relevance to specific projects and teams. Additionally, the orchestration layer within the tool plays a vital role in streamlining data processes.

For anomaly detection, the product provides only the last three weeks of data, while some competitors can analyze a more extended data history. This feature needs improvement. Its price could be a bit competitive compared to competitors offering similar services.

We have been using Monte Carlo for three years.

The product is scalable. However, they could improve the pricing and provide more cost-effective ways of scaling.

They offer efficient customer service. They provide essential documents, feedback, and solutions. They set up a meeting with us whenever we require more information.

Positive

The product's initial setup is in a daily improvement stage, deploying new plugins for upstream and downstream resources. It takes 25 minutes to complete. The process involves integrating with third-party services for Single Sign-On (SSO). It requires only one executive for maintenance as it has easy-to-use navigation and user interface.

The product has moderate pricing.

The product has centralized nodes and is a pioneer in the data observability domain. It has helped a lot in investigating system issues. It also saves a lot of time in identifying issues by improving data traffic.

I rate Monte Carlo a nine out of ten.