What is your primary use case for Dynatrace?

We use the product in application monitoring.

With Dynatrace, my company pretty much utilizes it to try and catch performance issues before certain issues get created on our online banking platforms, as well as for technical performance issues in our internal systems and to make sure that our users get the best experience. The aforementioned details consist of three use cases. Obviously, my company stopped using some of Dynatrace's features since we started getting a few issues as certain services have gone down or been degraded. With Dynatrace, my company receives pop-ups on our site in terms of an alert to which we can react if needed, and it helps us minimize any negative impact on our clients or business stakeholders.

We use the tool for performance analysis, root cause analysis, issue identification, and understanding the impact of technical glitches on business. We use performance dashboards and business dashboards.

Dynatrace is a strategic application performance monitoring tool. We use it for every use case related to monitoring applications. We use the SaaS solution to monitor on-premises. We also use Dynatrace for monitoring third-party applications and our own applications.

Our primary use case for this solution is for checking site vulnerability to see if the applications are up or down and if they're running fine.

Our primary use case for this solution is infrastructure and application monitoring. A total of 90% of our applications are on-premises and we are moving to the cloud, and this solution is helping us monitor that transition.

I primarily use the solution for mobile monitoring and service management.

My use case for Dynatrace is monitoring, including server monitoring. I use the tool to analyze what's wrong with the server, detect high memory utilization and any IO network problem, and monitor network traffic. I use Dynatrace to find errors and the root causes of the errors, including information on which carrier is giving slow response times.

We use Dynatrace for monitoring. It does have AI capabilities but the system needs more time to learn before we receive any benefit.

Regarding the use case for Dynatrace, currently, my company is working on a UK-based project in the telecom industry. I'm working as one of the leads on the Dynatrace side. The project has three vendors supporting it as it's a massive project. My role in the project is installing new agents, giving support for any BAU issues that arise, and creating dashboards. My company works with different vendors, such as IBM and TCS. It's the vendors that support RUM (real user monitoring) and licensing. On the other hand, my company handles agent deployments and gives that over to the application team. Whenever there's an issue, I assist in finding out the root cause and fulfilling requests such as creating new dashboards, customizing dashboards, etc.

Our company uses the solution to identify performance issues. Our database is in Oracle and our user interface is Maps. The solution helps us to gather required information and manage systems. For example, we just had a big data center issue with cluster settings, voting, and updating. The solution captured the issue and showed us that shutting down the data center would not solve the problem because data was not flowing from the DR side. This is one of the best use cases because the solution captured the issue so well that we didn't need help from another application or database team. We were able to identify the issue, correlate it, and provide information immediately.

It tells me everything I need to know. It tells me what the transactions are. The AI provides you with advancements or degradations in what is happening. It gives me visibility into everything, from transactional logs to services and processes to the OneAgent installed on the box, which tells me it's talking to systems that are in development and it shouldn't be.

Dynatrace is a very good solution to monitor both application performance and the underlying infrastructure. It's good to analyze all the relationships with Smartscape technology. It's very useful to understand all the dynamic relationships of the application stack, including all the hardware and dependent components. We always use the latest version. We deploy it on-prem and on cloud. The SaaS solution is deployed on AWS. The infrastructure manager or application or database manager will be using this solution. You can also have a CIO or CFO type of dashboard since there's business value and you can monitor the components. You can decide what is the total output provided by those applications.

We are using it for user monitoring and service monitoring.

My primary use case is application performance monitoring.

I am using Dynatrace for cloud monitoring, application monitoring, and alert notifications.

Dynatrace does application and platform diagnostics and monitoring and user experience management. Typically, in our region, we are seeing a lack of deep application platform management tools because most of the customers in our region don't use those tools. We are using Dynatrace Managed and Dynatrace SaaS. It is the new Dynatrace. They had a legacy product called AppMon, but nobody is using that now. Our customers mostly have on-prem deployments. In terms of the version, I always use its latest version.

The company uses it for a lot of things. Obviously, we're using it mostly for application monitoring, and that covers both application performance and availability. We're using it for checking how things are performing and making sure that they're running and running properly and there aren't errors or issues. That would be the main thing. We're also using it to monitor servers, do some infrastructure monitoring, make sure there're enough servers are running and that they've got available disc space for monitoring CPU and memory, et cetera.

Our primary use case is the consolidation of observability platforms.

We use this solution for our customers. Our customers are enterprise companies. We have several customers who are in automotive, finance and telecommunications which is the biggest one.

The primary use case is performance, capacity, and availability management along with user experience monitoring of 20 systems on a variety of technology stacks. User experience monitoring and optimisation of system performance and workflow. It has created good visibility on these topics for audit and compliance purposes, supporting adoption of a DevOps culture and practices within the team. We have FACT, COLLATE, and CODIX iMX technologies as well as in-house developed Java and .NET applications. These are hosted on Windows and Linux OSs and primarily on SQL Server and Oracle RDBMS.

We are using Dynatrace for application monitoring, elastic search, and problem analytics.

We are a solution provider and this is one of the products that we implement for our clients. We use Dynatrace both on-premises and in the cloud. Our use cases involve monitoring application performance. We are also able to see how the underlying infrastructure is performing. This monitoring capability gives us the ability to measure the end-user experience. We have other use cases, as well, but this is a summary of what we do with it.

My primary use cases of this solution are to understand how users are interacting with and experiencing applications and to quickly identify and fix problems.

The primary use case of Dynatrace is root cause analysis. Dynatrace is used for finding issues if an application is having trouble. I'm an integrator, so we have deployed it for customers both on-premise as well as on the cloud.

We use the solution in server monitoring, application monitoring, and roam and synthetic monitoring. We have 1,000 Dynatrace users in our organization.

We use Dynatrace for application monitoring in production and we use it in Huawei testing sites for analyzing the performance.

The solution is primarily used for user happiness monitoring. Basically, we look at how well we'll use it to run some arbitrary metrics over the website's behavior. I'm trying to understand how the user experience is going. Therefore, we're doing user experience monitoring. We're also using it for monitoring and listening, where we fire off specific test cases against that site with it. Typically, it does quite a lot. We can also do health monitoring of the actual service hosts, and servers, and dependencies. Dynatrace provides us with the ability to actually map out the whole ecosystem and our websites and services that exist within it. You have that whole picture even though it's now a distributed network of products and things. We use Dynatrace to just monitor the health of that ecosystem and manage, and identify where the dependencies are. In doing that, we can also look at hotspot monitoring, so that we can determine bottlenecks within our system. We can use it to follow metrics to help us figure out how fast things should occur, to identify slowdowns of speed - or potential slowdowns - which can cause us to have those little mysterious bugs where suddenly the user experience drops out because something three or four levels down is not behaving itself. Basically, it's a lot of use cases based on the user experience. There's lots of user monitoring. Lots of looking at where they're entering the sites from, where they're exiting the sites from. The behaviors can sometimes help us detect failures in our overall user experience. It's a lot of user experience management that's assisted via AI. We can use AI to develop, identify, establish, buy, and build trends so that we can look forward to purchasing requirements. Ideally, the AI will make it that we can identify where the system is going to fail in the future. We're still working on that side of things, but we're getting there.

We use it for infrastructure monitoring and real user monitoring on our website, i.e., monitoring how users interact with our website and digital experience. We use it to track if our website is up using synthetic monitoring, which we use for our website and mobile app. We use Dynatrace to track complete observability through our infrastructure to our digital apps.

We use Dynatrace as an analytics and monitoring tool. It is on-premise at the moment. We're looking at using the cloud-based one in the next year or so. We're in the process of migrating over to the cloud-based one.

I am using the solution for application monitor to identify performance and other information about applications that are running.

Our network and security managers used this solution. They had many problems with it because of the injection.

We have some states that use the solution for the whole monitoring of their infrastructure. It's used largely in the main court, state courts, and federal courts.

In the six months that we were using Dynatrace, it was a proof of concept. It's used for full-stack monitoring, automated instrumentation, APM, and byte code injections, as well as infrastructure performance monitoring and the virtualization layer.

We primarily use the solution to monitor performance and point our issues in the user experience of applications - specifically mobile applications. We are able to more clearly identify problems.

Our major use case for Dynatrace is end-to-end performance monitoring and other types of monitoring for business transactions, commerce transactions, websites, and so on. We have about five to twenty users, though their usage depends on a few different factors. Some users make intense use of Dynatrace while others use it on a less frequent basis. I use the managed version of Dynatrace, which means that it is deployed like a cloud solution but our data is stored on-premises.

We use Dynatrace for monitoring channels like mobile banking and internet banking.

We use it to discover the root cause of any problem. We are using the latest version.

We are in IT services. We implement and provide support to our clients.

We primarily use the solution to monitor business activity, transactions, and root cause analysis.

We use this solution for our customers for a wide range of tasks and for application optimization and such. It can be used in a performance test environment where developers run a new release to check they're headed in the right direction. I'm a senior analyst programmer and we are resellers of Dynatrace.

We are using the solution in the operations space. Our primary use case is production monitoring of complex business critical systems. Another use case would be performance testing of critical releases.

My use cases are typically working in conjunction with our business partners. For the most part, I get questions from the business as to what our conversion rates are on the eCommerce website. E.g., what the typical user journey looks like, especially when they're doing AB testing. They like to sort of double verify that in Dynatrace with a user session tracking to see which users are taking which path. I often get diagnostic questions about things like latency. Somebody on the business side will perceive some latency on one of our pages, then give me a call to use Dynatrace to go in and do a waterfall analysis of the page load to see if it is in fact loading more slowly than it has been in the past.

We're a health plan, a health insurer. We're not a big one, we have about a million members. We are growing through adding new business and we're looking to expand into the government programs: Medicare, Medicaid. Right now we provide individual and family, large corporate, self-insured, and a couple other types of health plans. We are headquartered in Minnesota, outside of Minneapolis. We have a data center in Minnetonka and one in another suburb. We do most of our work on-premise. We don't have much in the cloud for our core backroom applications. We use a package from a company called HealthEdge in Boston, to do our claims processing, membership, enrollment, etc. Our main use case is application performance monitoring, right at Dynatrace's sweet spot. First, we wanted to know what the performance of our healthcare and our health claims processing system was. Then we wanted to be able to segment it by where the transaction response time is spent. We also wanted to get into the deep dive of the Java profile, because HealthEdge is a Java application that runs on several JVMs. We wanted not only to get into the Java code but to get into the SQL that's created to call into the database, which is where the response-time problems are. We're using Dynatrace SaaS now. It's the newest version.

We use it to follow up user experience data. It's all banking applications. For example, when you're viewing your account, you open up your mobile app and the click you do to view your account is measured in Dynatrace. It's stored and we are checking the timing at each moment. We are also following up the timing differences between our different releases. When we have a new version release, we are already checking within our test environment to see what the impact of each change is before it goes to production. And we follow that up in production as well. In addition, we are following up the availability of all our different systems. And root cause analysis is also one of the main business cases. So we have three main use cases: * To follow up what's going on in production * Proactively reacting to possible problems which could happen * Getting insights into all our systems and seeing the correlation between these different systems and improving, in that way, our services to our end users. We use the on-prem solution, but it's the same as the SaaS solution that they are offering. They have Dynatrace SaaS and Dynatrace Managed, and our is the Managed. Currently we're on version 181, but that changes every month.

We have several uses for Dynatrace. Most of the time, we use Dynatrace for looking into potential site problems, investigating reported issues, and trying to replicate those problems in a test environment using the information provided by Dynatrace. We use Dynatrace for performance monitoring. Quarterly, we will specifically see if there's anything that we can optimize on the front-end of our website, so that's what you see and interact with on the web page. We also use it to get ahead of any potential problems in our stack. E.g., if Dynatrace is indicating a problem, we will look into it and determine if it's affecting users. Depending on its impact, and usually if it's impacting customers, we can use that information to decide on what we need to work on next to benefit the customer experience. I use the tool as more of an analyst. I will use Dynatrace to show where systems need to be fixed, etc. This solution is SaaS. We use Google Cloud Platform, where we just use their compute engines as far as our hosts. We also have a few services that are on-prem. Dynatrace works fine with both of them.

It's used in two major use cases: * Monitoring and our own internal IT operations. * We provide our customers access to Dynatrace tenants so customers can also leverage developing their code running on our platform. It does full stack monitoring for internal operations, problem diagnostics, APM use cases, and performance management for our customers. We have multiple instances of Dynatrace running, where about half of them are running in our data centers and the other half are running in the public cloud. Therefore, it's a hybrid deployment. We use a mixture of cloud providers, including AWS, Microsoft Azure (running Kubernetes), and Google Cloud Platform. We have traditional deployments on VMware virtual machines as well as running stuff in the cloud. We have a couple hundred Kubernetes clusters monitoring using Dynatrace. Dynatrace's functionality in this area is unmatched combined with its full stack visibility, ease of deployment, and completely dynamic changes. The container environments are also dynamic since you have microservices spinning up and down as you go. I have never seen another tool doing this with the same reliability.

We are using it to monitor our e-commerce applications and the full stack that our e-commerce applications run on. That includes both our Rack Room Shoes domain and our Off Broadway Shoes domain. We use it to monitor the overall health of the entire stack, from the hardware all the way to the user interface. And more specifically, we use it to monitor the real user's experience on the front-end.

Our primary use cases are operational awareness, health of the systems, and impact on users. Other use cases include proactive performance management, system checkouts (as we investigate the ability to manage configuration and integration to the CMDB), some usage of it from a product perspective in terms of application usage, and I use it to manage and improve the user experience by understanding user behaviors. We are in both Azure and AWS. We have both on-premise and cloud Kubernetes environments that we're running in. In fact, we have been using less efficient deployment methodologies. We haven't encountered any limitations in scaling to cloud-native environments. We have only used version 1.192 of the Dynatrace product. We have not used any previous versions.

When we started with Dynatrace we were an on-prem organization. We used it in the early days as an APM, the way most people used it. Our usage of Dynatrace has grown over the years, not as much in terms of capacity as in usability. It is now used by three departments within our organization. It originally started with just my group, which is IT, and then we rolled it out to development because they saw the advantages of being able to identify code bottlenecks in existing code. We've rolled it out to operations and they use Session Replay to troubleshoot customer-specific issues. And the sales department also uses it to gauge productivity and how many visits we get to a particular page, how many times people watch a particular video, how many take a certain practice exam, etc. Those use cases are all in addition to its core use, which is to help us keep our infrastructure running. We're currently using the Dynatrace SaaS, the Dynatrace ONE product. We're not using anything in the old, modular product. It fits very well for us. We are a cloud organization. We're all Azure now. We migrated from on-prem to cloud about three years ago.

Used to baseline and compare performance regression tests in development and to troubleshoot performance problems experienced by customers using our application in production. We monitor both on-prem and cloud environments during testing in Agile sprints as well as applying the tool in live production environments with permission.

I am a Dynatrace consultant, and I work with a partner in South Africa.

We use this solution for monitoring a monolithic application in ASP Classic 3.0 over IIS server. The database is SQL Server 2016 in an AlwaysOn cluster. Over three IIS instances for the core application, two IIS instances for reporting services, and two instances for the batch process in .NET 4.0.

We use this solution for APM and synthetic monitoring, as well as real user monitoring and other basic host monitoring. We have problems sent to PagerDuty via webhook in Dynatrace. This also goes to our on-call center. Debugging the worst transactions and other slow stuff is also done with this solution.

We use this solution for APM Monitoring on .NET, Java, and NodeJS, as well as Infrastructure Monitoring for Linux and Windows Based Systems, Kubernetes and Docker on-premise as well as in AWS. We perform automated monitoring using the Dynatrace API within our CI/CD jobs, and further, synthetic monitoring and HTTP Checks from different locations.

This solution is used to create dashboards for business-related applications.

We use this solution for application monitoring across regions. It can give a quick overview of the current health status, end to end, and can quickly point to the root cause if there an issue or problem in one of our applications. It helps our managers to keep track of everything on the dashboard.

We use this product to provide complete APM solutions for our customers.

This solution is used for: * Integrating the diagnostics for all of my team members with the same point of view through Dynatrace link. * System integration for automatic remediation; to launch Ansible Tower jobs in response to problems or events. * User experience tracking based on session behavior.

We use this solution for end-user experience, infrastructure monitoring, analysis of bounce rates, service calls to the database, root cause analysis, and problem management. For end-user analysis, I can monitor where the connections come from, the time, the number of navigated pages, bounce rates, and finally, if the usage was satisfactory or not.

This solution is used to monitor an IoT customer portal. It is hosted on Amazon Web Services. It is using Drupal, Microsoft SQL server, and eWON. By using Dynatrace Managed, we have given recommendations to developers and application owners on coding practices, but have also raised alerts on performance and availability.

I am a Dynatrace partner and the company where I work is a system integrator. We propose the Dynatrace solution to our customers for monitoring the performance of applications and integrate the solution with the other tools that they have.

We use this product for troubleshooting performance issues in our growing set of IoT portal solutions.

Our primary uses for this solution are Production monitoring and RUM (Real User Monitoring).

The primary use for this solution is for monitoring and performance challenges.

This solution is primarily used for performance analysis and problem-solving.

Our primary use case is to helps solve Java bugs.

We use Dynatrace OneAgent as a solution to monitor applications, as well as infrastructure. This idea was appealing to us for time management and efficiency purposes.

This is primarily used for Dynatrace Customer Managed Configurations in a closed customer environment. The operating systems include Microsoft Windows Server and various Linux distributions.

We are using this software to monitor an online banking system in a production environment.

APM monitoring and troubleshooting for any kind of technology.

Our implementation is not a single case. We are the local partner for Dynatrace in Romania and have very different use cases that differ based on our customers. Dynatrace is being used from monitoring the end user experience to infrastructure monitoring and real-time business and impact analysis.

We used this solution in a production environment to perform stress testing and evaluations to help find bottlenecks. We monitored user behavior and identified the funnel most used by our customers. In other services, we wanted to detect third-party tools with the wrong service.

We use this solution for performance monitoring and identifying resource management problems.

We run our application on a Windows 2008 to 2016 environment. We needed a tool to give us insight into how our applications were running. Dynatrace was the answer.

We are a partner and are selling this solution. We also use it internally.

We use this solution to assist with resolving incidents in a banking environment.

Our primary use case is to monitor the full stack of our digital platform, including the user experience. This provides us with business insights.

We use this solution for continuous monitoring in our customers' environments, auditing, and troubleshooting.

We use the Dynatrace platform to perform Application Performance Management for our Kubernetes clusters and some other legacy clusters. We have many Kubernetes clusters in our company and we are connecting each to an on-premise Dynatrace platform so that we can analyze the performance of each one separately.

Our primary use cases are for APM and digital experience management.

As a system integration company, we provide it as an APM solution to our customers.

We get APM requirements from various customers raising concerns about poor performance for their application. They do not know what is wrong and, most importantly, what is causing it. Dynatrace has helped a lot to identify performance bottlenecks and helped to fix them before the impact is increased.

We use Dynatrace to monitor the API performance of the server.

Our primary use case for both Dynatrace and AppDynamics is for application performance monitoring (APM). The main reason for having application performance monitoring is, when we see something is running slowly, we can immediately look to see where the issue is at before our systems crash on us. So, one of the major roles it plays for us is the ability to keep our system performing in peak shape. Our ability to see issues coming, then quickly isolate and correct problems was our main use of Dynatrace. We are not there yet with AppDynamics. It has been ten months, and we are still spinning our wheels trying to set it up and figure out how it works.

While working for an MSP, these customers' use cases vary - in most cases, we must do the fault domain to identify who is responsible in order to fix the root cause.

Our primary use case is operations monitoring.

The primary use case is monitoring and diagnostics for production marketing usage.

Our primary use case is application performance monitoring.

The primary use case is for application performance management. So, we are using it to identify outages of different parts of the application as well as how we can make the application more efficient and rightsize it.

We use it for application performance management (APM).

We use it to get the network stats and know how many clicks happened on both the front-end side and back-end side, then drill down on debiting to obtain the stats around that. Dynatrace is working fine right now. It is working as we expected.

We are using it track how the data flows throughout the entire AWS environment and seeing if there are any road blocks in between and trying to fix those. Dynatrace is really good at illustrating those. It provides a nice graph, and we can see where everything goes. It is easy to explain both to the people that work with it and the customers who want to see where their data is going.

We log everything. Anything that goes wrong, we want to make sure that we are able to see the reason why. Therefore, we check metrics around CPU usage, RAM usage, etc.

We use Dynatrace for application monitoring.

I use this solution for application monitoring.

Our primary use case is monitoring.

Our primary use case for the product is going through logs and tracing through what has happened.

Primary use case is EMI, which is application monitoring. Our enterprise management infrastructure is supported by Dynatrace.

We use Dynatrace for all our client-facing or student-facing core web systems, which give students access to their information. We are monitoring all those for user expectation and user experience management. We are also using application performance management metrics to detect and troubleshoot issues which pop up from time to time because it is a job. It's a Java-based environment that we're monitoring. Dynatrace AppMon has served us very well. We are able to get insights into our systems, which previously took us weeks to be able to detect. It gives us a much better view on the performance of our environments.

I installed the demo application on an internal server and looked at the functionality of Dynatrace.

Product is very high tech and advanced on the one hand, and very easy to implement and maintain on the other.

Web applications, primarily Microsoft MS-NET and Java-based applications, running on either IIS, WebSphere, and in lesser instances, Apache Tomcat or similar platforms.

Use case monitoring of our shop floor systems. We use it for acceptance and production environments, which are SAP based.

Our primary use use is to monitor apps in terms of performance and availability.

We have all our infrastructure in the cloud. This tool helps us gather information from all hosts and services, then cross reference the information.

* Application monitoring * Software performance issues * Learning application functions * Tracking issues

We are using it in our AWS environment for monitoring health and application performance for roughly 400 instances running thousands of Docker containers.

Customers want to monitor .NET applications and real user monitoring on online banking applications for desktop and mobile.

Our primary use case is performance improvements and understanding the customer struggle. Dynatrace gives us real-time data that we can use within the office to display data.

We mainly use the tool to do performance monitoring of our customer environments. Internally, we check how our software behaves when we are developing it.

Our core application is still running on a Java Client-server based architecture. We provide that application as a service by hosting it (hybrid cloud approach). We needed a tool that would provide insights into the application and support troubleshooting activities in order to reach our SLA objectives.

We use it to see a clear view of the system overall and monitor applications effectively and proactively. We also use it on our core software.

We are using Dynatrace to monitor our core application of the bank system. It is used especially in technical metrics monitoring.

Monitoring production environment at the hardware and application performance level for evaluation of performance during testing.

* Load testing in R&D to anticipate bottlenecks. * Used in production environments to retrieve consistent use cases.

* Operational monitoring: How services ran in the last five minutes. * NOC screens together with GTM monitoring. * Troubleshooting of problems occurring in communication between microservices down to the code level.

The primary use case is for application performance and analytics. We use it to monitor our on-prem Windows and Linux apps as well as our AWS and Azure cloud instances.

Performance monitoring of business critical applications in production and pre-production environments.

We are implementing this as part of an overall end user experience and application monitoring. Our environments include Java, .NET, web, mobile, Linux, Windows, etc.

Releasing a new product and going from an AS/400 to a Microsoft environment. We obtained a better insight into our environment and consolidated a lot of our old apps into one app.

Monitoring front-end for mobile banking within AppMon. We are using a balancer on NGNIX with a Dynatrace plugin to check availability by parsing logs.

It helps customers to understand performance, problems, and user behaviour. I implement an APM solution from Dynatrace to different customers in different industries, such as banking and telco.

* Full stack monitoring for several customers * Trusted consultancy * Development lifecycle support * Showing app problems during the testing phase

We are monitoring business critical applications which provide prepaid vouchers for different customers.

Web banking monitoring: With Dynatrace behind my customers' businesses, we are focusing on real user monitoring, dealing with user sessions, dashboards, and reports for their business.

Our primary use is application performance monitoring and real user experience. Our Dynatrace application monitoring has been in since 2012. It is performing extremely well. We have not had any downtime or issues with stability or scalability.

The primary use case of this solution is to investigate performance bottleneck issues.

Analysis, PurePath comparison, database hotspots, user experience monitoring, agent overview, incident management, building charts/dashboards, business transactions, etc.

Dynatrace is a 21st century APM tool designed and developed keeping next generation technologies in mind. We implemented it in our dev environment first, and the results were awesome. We got firsthand RCA as soon as we finished implementation.

Dynatrace is an extremely helpful APM solution in large, complex environments, whenever we need to have an integrated vision of our users, infrastructure, and applications. It excels when we need to do all this with the lowest resources possible, with the best data quality, across all layers, and with the least management overhead.