Best Practices for Tag Management

Tags can help streamline the workflow of any monitoring setup. With flexible naming and color-coding options that can be adjusted to your needs, they can quickly sort and categorize checks by contact groups, services, clients, or any other structure that fits your needs. Tags enable you to organize checks, streamline workflows, and take faster action when issues arise. Uptime.com offers 1,000 tags per account, so there is plenty of room for granularity when using them to sort and categorize your checks.

Here are some quick tips and examples of use cases to help you get the most out of tags in your monitoring solution.

Tag Checks by Team, Environment, or Client

Different teams may be responsible for checks based on organizational structure. For example, tags may be used to organize checks by the team responsible for responding to outages: Development, SRE, and NOC. This could also allow you to quickly filter to only the checks for which your team is responsible. You can also use tags to separate checks by environment: Production or Staging.

For a company providing monitoring services for many clients, you may want different contacts to receive alerts depending on the type of service or customer. Tags like High-Priority, Sales-Site, or Client-X can help organize checks and even help to more quickly hone in on issues with a specific site or customer.

Tags can have multiple checks assigned to them, so there is significant flexibility in assigning checks to multiple groups, environments, or clients as necessary.

Use Bulk Actions to Apply Changes by Tag

By tagging checks with increased granularity and sorting ability, applying bulk actions like setting maintenance or pausing becomes much easier. This reduces the need to hunt through multiple checks and also decreases the chances of human error when performing actions such as pausing/unpausing or setting maintenance schedules.

For example, putting multiple checks into maintenance at once due to a scheduled deployment can be quickly achieved by filtering and using bulk actions based on tag.

• Tag all related checks with something like Deployment or Backend-Migration.
• From the Monitoring page, use the Filters > Tags menu to narrow the view to only those tagged checks.
• Use the bulk actions menu to pause, delete, or apply a maintenance window across all selected checks at once.