The Terminology of Mobile App and Web Monitoring

Terminology for Mobile Monitoring

In today’s mobile dominant world, end-user experience is one of the critical drivers to your business success. It costs so little or even zero for users to switch between alternative products in case that they fail to have a pleasant interaction with your mobile apps or websites. The load speed, response time, service availability, all of these affect how end users judge your products or even brands. And this is where mobile monitoring comes to play a role.

Regardless of synthetic monitoring or real-user monitoring, they provide with you invaluable insights for you to analyze and fix the issues as soon as they are identified to minimize the loss due to unstable performance.

Today we are going to review some terms of mobile monitoring. If you just start a new role related to mobile performance management in your company, you will find this terminology helpful.

Terminology of Mobile Monitoring

Synthetic Monitoring

Synthetic monitoring, also known as active monitoring or directed monitoring, is an approach to periodically monitor mobile applications, websites or API endpoints by checking an action that a customer or end-user would take in real world. It can be done in both scripted and unscripted way.

Real-User Monitoring

Real-user monitoring (RUM), also known as passive monitoring, is a method to continuously observe your system in action and gather all information when users interact with your mobile applications, websites or API endpoints. Real-user monitoring is unscripted.


In synthetic monitoring, a check means a performance test run that you execute to monitor how your mobile apps, websites or API endpoints work at a given moment, while it means a record with user information gathered by the web-monitoring services whenever users interact with your mobile apps, websites or API.


Due to the different methodology of synthetic monitoring and real-user monitoring, the interval has different meanings.
In synthetic monitoring, the interval literally means an amount of time between any two performance checks that are executed to monitor your mobile apps or websites.
However, the interval doesn’t have straight-forward meanings in real-user monitoring. It means a single pageview that each time a visitor views a page on your website while using mobile devices, while it means any transactions that your mobile application interacts with your back-end system while it is in use or running in the back-end on users’ mobile devices.


A notification that is pre-defined to help you notice what negative performance has happened during the last check.


A downtime refers to a certain moment or duration in which your mobile applications, websites or API endpoints are out of action and fail to function properly as it should.

Availability (Ratio)

In the landscape of mobile monitoring, availability usually means the ratio of the total amount of time your mobile applications or websites succeed to perform as it should in a given period of time. It’s normally expressed as X%, such as 99.99%.


A noise indicates a data point tracked in real-user monitoring method that hinders the lookout of the real performance issues in your mobile and web apps, due to the complexity combined with various factors, including the way of how your mobile app or web is built, user’s environment, user’s behavior, etc.


DevOps is an approach to enable seamless collaboration and communication between your software developers and other IT professionals for the continuous delivery. Whenever operations team are notified by the downtimes or negative alerts, it helps them act quickly to work with development team to get your mobile app or web up and running in an agile way.

Service-Level Agreement (SLA)

A service-level agreement is a standardized contract between a service provider and an end-user that documents the level of service set by the customer and agreed by the provider. In the world of mobile and web app monitoring, it basically means at what level of the availability is agreed or what unavailability is accepted.

Bitbar monitoring is under development. And the beta version will be available soon. You can leave your info to apply for the beta here if interested. We also appreciate your participation to our survey to provide your valuable feedback.

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.