monitoring with subaccounts

How to Manage Your Monitoring with Subaccounts

The need to implement 360° monitoring for a multi-service infrastructure is almost a universal truth among growing companies. With an expanding pool of clients and services to monitor, segmentation is the key to smooth operation. Monitoring with subaccounts is prime management solution.

The trick is to simplify your account structure without limiting your visibility. To evaluate, we’re going to dive to a cellular level. 


A Quick Bio Lesson

Size matters. Biological cells are broken down internally into compartments of resources. The compartments make the cell efficient by separating different processes into concentrated areas. If a cell grows too large too quickly, it will have more trouble processing its stored resources and nutrients. 

Cells that are not able to process their resources efficiently either completely divide, or become obsolete and self-destruct by activating an internal process known as programmed cell death. In terms of account function, this level of ‘cell death’ is costly.

Subaccount Structure

Subaccounts create channels among tech teams for managing separate collections of checks and data, as well as organizing assets by client or service. A subaccount’s structure is interdependent; connected to a main account and managed by account administrators acting as omniscient overseers. has several features in play to create transparency between our users and their own customers, stakeholders, etc. Reporting assets like our Scheduled SLA reports provide the vehicle for sharing uptime and response time metrics when, how, and with whomever, and subaccounts help simplify report creation. 

With subaccounts, checks and permissions can be controlled to expand on accountability, but also provide permission-based access to necessary third-party vendors, support technicians, and team members with focussed responsibilities related to monitoring.


A Controlled Solution

One of the greatest advantages of creating subaccounts is security. A topic at the forefront of technology discussions, security is always an influencer when it comes to account structure and access. 

Subaccount users can be created with differing levels of permissions:

  • Every permission level can view all subaccounts. 
  • Users with View only or View and Modify access can only access the subaccounts they are assigned
  • Subaccount Admins have the ability to edit all subaccounts
  • Subaccounts can be secured with SSO


A structure like this establishes a drill-down mindset when it comes to account management and allocation of resources. This separation also lends itself to effective alert management.


Monitoring with Subaccounts: Benefits

Let’s isolate the benefits of subaccounts starting with specialized monitoring for targeted checks and services.

Each subaccount is governed by a main account and account owner who has access to the full-suite of monitoring features under the main account’s plan limits. Parameters can be assigned to subaccounts in highly personalized ways. Want a subaccount made up of HTTP(S) checks to monitor multiple domains? You got it. A subaccount of only Transaction checks to provide synthetic monitoring for shopping carts and login forms? Done. 

Design your subaccounts to meet specific needs for SLA reporting and Status Pages with customizable dashboards to control independent monitoring cycles nested within a larger main account.


Limiting Damages

Subaccounts are like a protective membrane around isolated checks. Yes, they come with their own reporting, but also their own alerting structure which helps mitigate downtime and increase response time in the event of an incident. 


Clear designation of responsibilities

Subaccount responsibilities are managed by Administrative users who have the power to access and edit all subaccounts, as well as more restricted users who are assigned to specific subaccounts.

In any type of account when a check experiences downtime, the check’s contacts are alerted. If a check stays down for a determined period of time, alert escalations kick in and notify a designated higher level user. Subaccounts follow the same protocol with an alert hierarchy contained to that account. Users can also be linked via contacts to third-party integrations such as PagerDuty and Microsoft Teams.

User permissions act as gatekeepers and control access to features such as editing capabilities, Status Page updates, check management, and reporting to reduce the potential for error, and maintain a healthy monitoring process.


Minimize Non-related Communication

More is not always better. When it comes to your notifications you want to reduce false-alerting to ensure reporting accurately reflects your monitored services. You don’t want to deal with alert fatigue from thousands of checks at once. Since subaccounts are structured to be separate, alerts are easier to manage which improves accuracy. 

Subaccount provide another silver lining related to communication, and we can boil it down to human action.


Team Interactions & Expedited Support

Subaccounts clearly define the scope of responsibility which cuts down on the need for exploratory questions from team members trying to understand an error or locate a check from a sea of similar data.

Narrowing the monitoring field helps to establish manageable routines, develop incident response run-books, and perform gameday exercises by reducing the quantity of checks, and increasing the amount of attention that can be expended on the monitoring infrastructure contained within the subaccount.

When it comes to data, some separation can provide clarity and accuracy while reducing response time. When it comes to visibility, a unified monitoring approach is mandatory. Subaccounts give you both by keeping your information manageable and connected.


Monitoring with Subaccounts: Segmentation not Division

Over-dividing your accounts into many smaller accounts and hyper organizing your data will leave you with a disjointed account structure that is just as challenging to manage as a single massive account.

The purpose of subaccounts is to provide a connected “warehouse” tasked with managing a specific flow of checks and monitoring assets dedicated to a client or service. 

Have questions? Simplifying complex accounts is one of our superpowers. Connect with our support team to learn more, or reach out to our sales team to add subaccounts to your monitoring infrastructure.  

Minute-by-minute Uptime checks.
Start your 14-day free trial with no credit card required at

Get Started

Don't forget to share this post!

Emily Blitstein is a technical content writer for With a background in writing and editing, Emily is committed to delivering informative and relatable content to the user community.

Catch up on the rest of your uptime monitoring news