Skip main navigation

Hurry, only 10 days left to get one year of Unlimited learning for £249.99 £174.99. New subscribers only. T&Cs apply

Find out more

Application Target Considerations


In the last step, we compared RUM and synthetic transactions. We joined a discussion where we considered what metrics are better to gauge using Real User Monitoring (RUM) rather than Synthetic Transactions. In this step, we will look at application target considerations.

When deciding how to implement application monitoring and which tools to use, it’s important to recognise that there are different targets for your applications and thus, monitoring will depend on the targets, especially data collection.

If your application is written in .NET, Java, Microsoft Windows, Azure, or Amazon Web Services, monitoring will differ depending on how the application is written and where it’s being hosted. For most monitoring tools, there will be different software development kits (SDKs) for every language. Before you decide how to monitor and which tool to use, make sure to research which tools work best for the frameworks, languages and implementations of your application.

In the following step, we will examine the topology of deployments to determine if considerations for monitoring are relevant.

This article is from the free online

Microsoft Future Ready: Fundamentals of DevOps and Azure Pipeline

Created by
FutureLearn - Learning For Life

Reach your personal and professional goals

Unlock access to hundreds of expert online courses and degrees from top universities and educators to gain accredited qualifications and professional CV-building certificates.

Join over 18 million learners to launch, switch or build upon your career, all at your own pace, across a wide range of topic areas.

Start Learning now