Our DevOps and our development team used Catchpoint exclusively for synthetic testing of API and URL endpoints. Our DevOps team is like a composite team for the solution users. Their job was to operate the tool and build the test, and they were the primary folks using it daily. 

The developers used Catchpoint for pre-production testing to ensure that the tests ran and gave them the needed data. They made improvements to the systems that were being monitored. We had around 100 users on the whole platform. The third group was my team, the platform owners. We were in there running daily reports. 

When we started, it was pretty light because we were trying to evolve our thinking, and then it grew. The contract was renegotiated when I was leaving, and we were increasing the test count even higher than we had, indicating a higher level of interest in what we could get out of it. 

Catchpoint is a natively built cloud. There are also ways to deploy an agent internally for tests that sit behind firewalls and internal systems, but the platform is definitely SaaS.

We're using Catchpoint for monitoring activities. From a user perspective, we're using the tool to monitor online shopping customers and support global customers. Suppose customers face issues when purchasing, we get alerts from Catchpoint. Wherever there are red alerts, there are issues in specific markets, so these are the notifications we receive in Catchpoint. Through the tool, we can further drill down to see the flows we need to validate, and we can also see the input parameters the customers are using. We can also use Catchpoint to get test data in real time and validate those quickly.

There are scatter plots in the tool where there are frequent drops or frequent notifications for specific markets, so we can just go over the scatter plots, see the time duration where we can identify, for particular markets, that the drops are consistent, and that would mean there aren't critical issues going on, so based on that information, we can take the actions we need.

Our company tests versions of international websites for our clients and we use the solution's simple node backbone to track website response metrics and waterfalls. 

Our use case is unique because most companies conduct constant, proactive monitoring but we are responsive and only monitor when we experience issues.

Our primary use case for the solution is for end vision monitoring with an endpoint solution. We also use them to create network status while focusing on the synthetic solution because of digital monitoring. Catchpoint provides a great amount of information, and customers want budgets, so they spend less on cheaper products. Catchpoint has a better chance to increase its market, but they have been focusing on the synthetic force because there is a clear advantage and digital monitoring. We deploy the solution on-premises.

Currently, our organization is adopting Asawari principles. We are using Catchpoint as a marketing tool. 

We create automation scripts for our applications. Those scripts are running in Catchpoint, enabling us to hit different geolocations, ensuring that prospective customers are reliable when they come to our sites.

Catchpoint provides the data for our internal dashboard which shows us the reliability of the customer.

We were using this solution to monitor the shopping element of our partner sites.

We are using this to monitor our applications, our global applications, like the Autodesk Store, Autodesk.com application websites, Autodesk subscription portal, Autodesk account management. So all those global websites that our customers access are monitored through Catchpoint. It's used as a global synthetic monitoring solution.

We use Catchpoint to monitor our websites in real-time. It helps us keep track of various metrics. 

Catchpoint is used for synthetic monitoring. For example, if you have a URL, you may want to ensure that your customer's journey is monitored from a user-experience standpoint. 

In Catchpoint, you can enter the user action, and that user action can then be configured as a script. Catchpoint will then continue to emulate that user's steps every 5 minutes or 10 minutes, as it is defined by you.

If you have a service product and have just exposed the API in your data. In those cases, you can perform API monitoring by passing sample data contracts and validating whether your API is responding to the query or not. It can also tell you what the time is, what the response score is, and so on.