Below is a list of commonly used Atatus terminology you would come across.

Account

Atatus is designed for use by organizations, and each organization can have one primary account with multiple sub-accounts. These sub-accounts are linked to the primary account, but they have their own settings and configurations. The primary account has the ability to manage the sub-accounts, set up access controls and permission levels for each user, and view the data and performance metrics for each sub-account.

Both primary and sub-accounts can have multiple users, each with its own level of access and permissions. Users of the primary account will have access to all sub-accounts, but users of sub-accounts will only have access to the data and performance metrics of their specific sub-account. This allows organizations to easily manage and monitor the performance of multiple applications or services, while also maintaining a level of separation and data isolation.

Additionally, the primary account user can grant access to the sub-accounts to other users, for example, for a specific team or division, this way different teams can have access to different applications and monitor them separately.

Alert Policy

An alert policy refers to the set of rules and conditions that are used to trigger an alert or notification when certain events or conditions are detected by the monitoring system.

Alert Rule

An alert rule typically checks a specific metric or data point, such as the response time of a web server, the number of errors in a log file, or the CPU usage of a server against a threshold value or a range of values. When the metric or data point matches the defined conditions, the rule triggers an alert, which is then sent to the specified notification channel, such as email, SMS, instant messaging, or webhook.

Ajax Requests

The AJAX UI displays a list of the most recent AJAX requests made by web app, including both HTTP and HTTPS. This data can be used to pinpoint issues with the user experience, such as slow-loading or failed AJAX calls that affect the dynamic elements of a webpage on your website. These metrics can include the time it takes for the request to be sent, the time it takes for the server to respond, and the time it takes for the response to be processed by the browser.

API Analytics

API analytics refers to the process of collecting, analyzing, and reporting on data generated by application programming interfaces (APIs) that are used to connect different systems and applications. API analytics tools can be used to monitor API usage, performance, and security, and to gain insights into how APIs are being used and how they can be improved.

The metrics that API analytics tools offer can include:

  • API request and response rates
  • Response time and latency
  • Error rates
  • Resource usage (e.g., CPU, memory, disk)
  • Security events (e.g., failed authentication attempts)
  • User behavior (e.g., number of API calls per user, usage patterns)
  • Endpoints usage (e.g., popular endpoints, endpoints with errors)

These metrics can be used to improve a web application by:

  • Identifying and troubleshooting performance bottlenecks and errors in API calls
  • Optimizing resource usage to improve scalability and reduce costs
  • Detecting and preventing security threats
  • Analyzing user behavior to identify and address usability issues
  • Identifying popular and underutilized endpoints and making adjustments to improve the overall API performance
  • Identifying areas for improvement in the API documentation and developer experience

API Requests

API requests refer to the number of times an API (Application Programming Interface) is called or accessed by a client. This can include things like mobile apps, web applications, and other systems that rely on the API to retrieve or update data.

The number of API requests is often used as a metric to measure the popularity and usage of an API, as well as its performance and reliability. It can also be used to identify any issues or problems with the API, such as high error rates or slow response times, that may be impacting the user experience.

Additionally, analyzing the API requests can help to identify the most common use cases of the API, and how it is being used by the clients.

APM

An APM (Application Performance Management) is a type of software that helps monitor and optimize the performance of web applications. APM tools typically offer a variety of metrics, such as response time, error rate, and throughput, which can be used to identify and diagnose performance issues.

Some common metrics offered by APM tools include:

  • Response time: The time it takes for the application to respond to a user request.
  • Exception and error rates: The number and types of exceptions and errors that occur during application execution, which can indicate issues with code quality or configuration.
  • Latency: The time it takes for a request to be completed from the time it was initiated.
  • Throughput: The number of requests that can be handled by the application per second.
  • Database queries: The number and duration of database queries, can indicate issues with database performance or inefficient query structures.
  • External service calls: The number and duration of calls to external services, which can indicate issues with service availability or network latency.

These metrics can be used to improve a web application in several ways:

  • Identifying and diagnosing performance bottlenecks: By monitoring the metrics, developers can identify areas of the application that are causing slow performance or high error rates.
  • Improving scalability: By monitoring throughput and resource usage, developers can identify areas of the application that need to be optimized to handle increased traffic and usage.
  • Enhancing user experience: By monitoring response time and error rate, developers can ensure that the application is providing a fast and reliable experience for users.

APM Transaction

APM transactions provide an in-depth analysis of individual actions within your application, including performance metrics, opportunities for improvement for under performing transactions, and the ability to drill down into specific components and services. The data is presented in a clear, easy-to-understand tabular format for convenient analysis.

Atatus Agent

Atatus agent is a piece of code that should be installed in your application or host for observability. There are separate agents for the different languages, frameworks and operating systems.

Browser Monitoring

Browser Monitoring (Real User Monitoring - RUM) is a type of software that helps monitor and optimize the performance of web applications by tracking how the application behaves in the real world, from the user's perspective. It captures performance metrics such as page load time, user interactions, and JavaScript errors. These metrics can provide insight into how the application is performing in the wild and can help identify issues that may not be visible through other types of monitoring.

Some common metrics offered by RUM tools include:

  • Page load time: The time it takes for a page to fully load and be ready for user interaction.
  • Time to first byte (TTFB): The time it takes for the browser to receive the first byte of data from the server.
  • Time to interact (TTI): The time it takes for the page to become fully interactive and responsive to user input.
  • Resource load time: The time it takes for individual resources such as images, scripts, and stylesheets to load.
  • JavaScript errors: The number and types of JavaScript errors that occur during the page load and user interactions.
  • User's browser and device information, geolocation, and network information: This can provide insight into how the application performs on different devices, browsers, and network conditions.

These metrics can be used to improve a web application in several ways:

  • Identifying and diagnosing performance bottlenecks: By monitoring page load time, TTFB, and TTI, developers can identify areas of the application that are causing slow performance or are blocking the page from being interactive.
  • Improving user experience: By monitoring resource load time, JavaScript errors, and user's browser and device information, developers can ensure that the application is providing a fast and reliable experience for users across different devices and browsers.
  • Enhancing User interaction: By monitoring user interaction, developers can identify which parts of the application are causing delays or are not working correctly.

Browser Transaction

In browser monitoring, "browser transactions" refer to the tracking and measurement of specific user interactions or flows within a web application. These interactions can include things like visiting a specific page, filling out a form, clicking a button, and so on.

Browser transactions allow you to see how long each step of a user flow takes, as well as how well each step is performing. This information can then be used to identify and fix any issues that might be impacting the user experience.

Browser transactions are an important part of browser monitoring as they allow us to see how the user interacts with the web application and measure the performance of each step of the user flow. By identifying and fixing performance issues, you can improve the user experience and increase conversions, engagement, and retention.

Checks

A check in Synthetic monitoring refers to a specific test or set of tests that are run to measure the performance and availability of a website or, web application. These checks are typically run on a scheduled basis (1 min, 3 min, 5 min, etc) to continuously monitor the performance of the service and detect any issues as soon as they occur.

Each check can be configured with different settings, such as the URL or transaction to test, the frequency of the check, and the locations from which the check should be run. The check can also be configured to have specific alerting rules and notifications so that when a check fails, an alert will be sent to the appropriate team members.

By continuously running these checks, synthetic monitoring tools can help you make sure your services running 24/7 without any down time. If any services are down, Atatus will notify you through email, slack, teams, etc.

Check Runs

In Synthetic Monitoring, Check run refers to a specific instance of a check being executed. Each time a check is scheduled to run, it is considered a check run.

Check runs are a way of tracking the history of a check and its results, including whether a check run passed or failed. The check run also includes information such as the location from where the check was run, the response time, global uptime, events, and incidents of the check.

CPM (calls per minute)

Calls per minute refers to the number of database calls or external calls sent by your back-end application per minute.

Databases

The Databases section of an APM solution allows you to gain insights into the performance of the database queries made by your service. You can view metrics such as the total or average time taken by specific database calls, the number of queries per second (throughput), and the most time consumed query, this way you can easily identify which calls are impacting the performance of your service. Additionally, you can drill down into the performance of an individual call and see traces that include that call, this can aid in troubleshooting and identifying the root cause of performance issues.

EPM (errors per minute)

The number of errors occurring in a minute. It could be JavaScript errors or other request failure(4xx, 5xx errors) due to issues in your application.

External Requests

The External Requests UI page provides a comprehensive view of the performance of external requests made by your website. The page includes response time and throughput charts, as well as a table view that lists all related services in a columnar format. By clicking on a specific URL, you can also see which transactions have made that particular request, allowing you to identify and troubleshoot any issues.

Health Checks

It is an infrastructure feature that is used to check the health (uptime) of the your micro services. If these micro services has publicly accessible end point, then you can use Synthetic monitoring checks. If it does not have public end point, then you need to use Infra health checks. You can read more about it here

Hosts

We calculate a host as a physical machine or VM that is sending data to us for 720 hours in a month. That means, if you autoscale and say if you run 2 physical hosts for the first 15 days of the month and then no hosts are running for the second 15 days of the month, then you would have connected only 720 hours and so only one host will be calculated.

Incident

An incident in a monitoring tool typically starts when an alert is triggered by an alert rule within an alert policy, indicating that a particular condition or threshold has been exceeded. The alert is then sent to the specified notification channel, such as email, SMS, instant messaging, or webhook, to notify the appropriate individuals or teams.

Infra Monitoring

Infrastructure monitoring is a process of collecting and analyzing performance metrics from the various components of a web application's infrastructure, including servers, networks, and storage devices. These metrics can provide insight into the health and performance of the underlying infrastructure and can help identify issues that may impact the performance or availability of the web application.

Some common metrics offered by infrastructure monitoring tools include:

  • CPU usage: The percentage of CPU resources being used by the system.
  • Memory usage: The amount of memory being used by the system.
  • Disk usage: The amount of storage being used by the system.
  • Network traffic: The amount of data being sent and received over the network.
  • Error rates: The number of errors occurring on the system.
  • Response time: The time it takes for the system to respond to requests.

These metrics can be used to improve a web application in several ways:

  • Identifying and diagnosing performance bottlenecks: By monitoring CPU usage, memory usage, disk usage, network traffic, and error rates, developers can identify areas of the infrastructure that are causing slow performance or are blocking the page from being interactive.
  • Improving scalability and availability: By monitoring the performance of different components of the infrastructure, developers can identify bottlenecks that may impact scalability or availability and take steps to address them.
  • Plan for future growth: By monitoring the usage of resources, developers can anticipate future growth and plan accordingly.

JS Errors

JS errors in Error Tracking allows you to easily locate and troubleshoot JavaScript errors on your website, by providing detailed information about the location and cause of the errors.

Upon clicking on a specific JS error you can view the complete stack trace of the error, the exact line of the code where an error occurred, breadcrumbs, and user information.

Key Transaction

it could be any important or frequently occurring events. You can save your favorite transactions as key transaction.

Logs Monitoring

Logs monitoring is the process of collecting, analyzing, and reporting on log data generated by various systems and applications. Log data can include information about system and application performance, security events, and user activity. Log monitoring tools can be used to identify and troubleshoot issues, detect security threats, and gain insights into system and user behavior.

Logs monitoring can be used to improve a web application by:

  • Identifying and troubleshooting performance bottlenecks and errors
  • Optimizing resource usage to improve scalability and reduce costs
  • Detecting and preventing security threats
  • Analyzing user behavior to identify and address usability issues
  • Correlating application performance with infrastructure metrics to identify the root cause of an issue
  • By using logs monitoring, you can get a better understanding of how your web application is performing, identify areas for improvement, and take action to optimize its performance and security.

Notification Channel

A notification channel refers to the method or medium used to send alerts or notifications when certain events or conditions are detected by the monitoring system. It can be set up to send notifications via email, webhook, or even through third-party tools like slack, PagerDuty, etc.

Page

Pages in browser monitoring offer a detailed analysis of the performance of your website's pages. Typically, pages are grouped together if numbers/uuid are found in the path. Lets say /users/1 and /users/132 are grouped together under page /users/*. However you can also see all individual pages and its performances.

You can view detailed information about the most visited pages, timing, and throughput details. This information can help you identify and troubleshoot performance issues, optimize specific pages, and improve the overall user experience.

If you click on a specific page, you'll be able to view web vital metrics, performance, sessions, AJAX breakdowns, and top 5 stats for that particular webpage.

PPM (page views per minute)

The number of pages viewed in your front-end application per minute.

Response Time (in APM)

It is the amount of time taken by any application to respond to any request.

RPM (requests per minute)

The number of requests received by your application from the users in a minute. The request is also called as transaction.

Routes

The Routes in browser monitoring provides information about the different routes, or URLs, that are being accessed after page load on single page web application (SPA). It allows you to see which routes are being accessed most frequently, how long they take to load, and how many errors are occurring on each route. This information can be used to identify performance bottlenecks, optimize the performance of specific routes, and diagnose errors.

The Routes typically displays a list of all the routes that have been accessed on the website or web application, along with performance metrics for each route such as:

  • Average route time
  • Route throughput
  • AJAX breakdowns

SAML

By setting up SAML on your Atatus account, you and your colleagues can access the platform using login information already stored in your company's Active Directory, LDAP, or other identity systems that has been integrated with a SAML Identity Provider.

Sub Account

Sub accounts in Atatus are intended to provide a way for teams within an organization to manage and monitor specific projects or clients. They allow you to create separate, isolated environments for different projects or clients, each with its own settings and performance metrics. This is particularly useful for organizations that have multiple projects or clients that they are working on simultaneously.

When you create a sub-account, you can assign users to it and they will only have access to that specific sub-account. For example, you can create a sub-account for a specific client or project and assign a team of developers or support engineers to it. They will be able to access only the data and performance metrics for that specific client or project, and not the other sub-accounts. This ensures that team members only see and work on the data that is relevant to them and improves security and data isolation.

Also, you can create different sub-accounts for different stages of development for example, development, staging, and production, and give access to different teams for each stage. This way, different teams can monitor and troubleshoot different stages separately.

Sessions

Sessions User Interface (UI) offers a comprehensive chronology of the loading and interactions that occur during a web page's entire life cycle, for a duration of up to ten minutes. With the session URL selected, the waterfall visualization and metrics associated with session statistics are displayed, including:

  • Page load times
  • Network time
  • DOM time
  • Total duration
  • User information such as user name, OS, browser and device type, country, and ISP.

This information can help you identify and fix performance issues, improve the load time of specific pages and enhance the overall user experience.

Synthetic Monitoring

Synthetic monitoring is a method of monitoring the performance and availability of web applications and other online services by simulating user interactions with the application from various locations and devices. Synthetic monitoring tools can be used to proactively identify and troubleshoot issues, and to measure the end-user experience.

Synthetic monitoring metrics can be used to improve a web application by:

  • Measuring end-user experience and identifying usability issues
  • Monitoring availability and uptime
  • Identifying and tracking trends in application performance
  • Correlating application performance with infrastructure metrics to identify the root cause of an issue
  • Setting up alerts and notifications when certain thresholds are reached

Throughput

Throughput is the number requests or calls over a given period of time. It can be used to measure the counts of various components (e.g web app's page views, server's request count, db calls, external requests count).

Throughput metrics can be used in conjunction with other metrics, such as response time, error rates, and resource utilization, to provide a more complete picture of the performance of the web application and to identify issues that may impact the user experience.

Users Unique

A unique user in Real User Monitoring is a person who visits a website or web application. The unique user is typically identified by a unique identifier such as a cookie or IP address.

The number of unique users is often used as a metric to measure the popularity or engagement of a website or web application. It is different from the number of total visits or pageviews, as it only counts one visit per unique user.

Users Affected

In browser monitoring, users affected typically refers to the number of unique users who have been impacted by a problem or issue on a website or web application. This can include users who have experienced errors, slow loading times, or other issues that negatively impact their experience.

This metric is used to determine the severity of an issue and the number of users who have been impacted by it. It can also be used to measure the effectiveness of a solution or fix in resolving the issue and restoring normal function for the affected users.

Views

A page load or a route change is considered as a View. A View is a single visit to your website/app by your user. If the user refreshes/revisits your page again, then it is considered a separate View. When there is a route change event in a single page app, it is also considered as a View.

We allow equal number of Errors as Views. If you have a project where there are lower Views than JS Errors, then JS Errors will be considered as the Views count. Lets say if you are subscribed to 1M Views, then we accept JS Errors up to 1M within the same plan. If at the end of the month you have 1M Views and 2M Errors, then your usage will be considered as 2M Views.

Web Vitals

Web Vitals are a set of performance metrics that measure the loading, responsiveness, and visual stability of a web page. These metrics can help identify and troubleshoot performance issues and improve the overall user experience.

  • FCP

    FCP (First Contentful Paint) is a web vital metric that measures the time from when the user requests a page to when any visible content is rendered on the screen. It is a measure of how quickly the user perceives that something is happening on the page.

  • LCP

    LCP (Largest Contentful Paint) is a web vital metric that measures the time from when the user requests a page to when the largest visible element (such as an image or heading) is rendered on the screen. It is a measure of how quickly the main content of the page is visible to the user.

  • FID

    FID (First Input Delay) is a web vital metric that measures the time from when a user first interacts with a page (such as clicking a button) to when the browser is able to respond to that interaction. It is a measure of how responsive the page is to user input.

  • CLS

    CLS (Cumulative Layout Shift) is a web vital metric that measures the visual stability of a page. It measures the number of unexpected layout shifts of visible elements.

  • TTFB

    TTFB (Time to First Byte) is a metric that measures the time from when a user requests a page to when the first byte of the response is received. It is a measure of how quickly the server is responding to requests.

  • INP

    INP is a metric that assesses a page's overall responsiveness to user interactions by observing the latency of all click, tap, and keyboard interactions that occur throughout the lifespan of a user's visit to a page. The final INP value is the longest interaction observed, ignoring outliers.