GUIDEServer Management

Organizing Servers with Labels

5 min read

As your infrastructure grows, managing multiple servers can become challenging. Data Mammoth's labeling system lets you organize your servers by assigning custom labels — making it easy to filter, identify, and group servers by project, environment, client, or any other criteria you choose.

Why Use Labels?

Labels are especially useful when you manage more than a handful of servers:

Quick identification — Instantly recognize a server's purpose without clicking into its details.
Filtering — Filter the server list to show only servers matching specific labels.
Organization — Group servers by project, team, environment, or region.
Team communication — Labels help team members understand the server landscape at a glance.

Adding Labels to a Server

Navigate to Servers.

Click on the server you want to label.

Go to the Settings tab or find the Labels section on the overview page.

Click Add Label or the edit icon next to the label area.

Type a label name and press Enter or click Save.

You can add multiple labels to a single server.

Label Naming Conventions

Establish a consistent naming convention for your labels to maximize their usefulness:

By Environment

Label	Purpose
`production`	Live, customer-facing servers
`staging`	Pre-production testing environment
`development`	Development and experimentation
`testing`	Automated testing infrastructure

By Project

Label	Purpose
`project-alpha`	Servers for Project Alpha
`client-acme`	Servers managed for a specific client
`internal-tools`	Internal company tools

By Role

Label	Purpose
`web-server`	Servers running web applications
`database`	Database servers
`load-balancer`	Load balancing servers
`cache`	Caching servers (Redis, Memcached)
`worker`	Background job processing servers

By Priority

Label	Purpose
`critical`	Mission-critical infrastructure
`standard`	Standard importance
`low-priority`	Non-essential, can tolerate downtime

Using Multiple Labels

Combine labels from different categories to create a rich organizational system. For example, a server might have the following labels:

production
project-alpha
web-server
critical

This immediately tells anyone looking at the dashboard that this is a critical production web server for Project Alpha.

Filtering Servers by Label

Once you have labeled your servers, use the filtering system on the server list page:

Navigate to Servers.

Look for the Filter or Labels dropdown.

Select one or more labels to filter by.

The server list updates to show only servers with the selected labels.

This is particularly helpful when you need to:

Perform maintenance on all production servers.
Check the status of all servers for a specific project.
Review all database servers across your infrastructure.

Renaming Labels

To rename a label:

Navigate to a server with the label you want to rename.

Go to the Settings or Labels section.

Click on the label to edit it, or remove it and add a new one with the updated name.

Note that renaming a label on one server does not automatically rename it on all servers. You will need to update each server individually, or use the bulk management features if available.

Removing Labels

To remove a label from a server:

Navigate to the server.

Go to the Labels section.

Click the X or delete icon next to the label you want to remove.

The label is removed immediately.

Removing a label does not affect the server itself — it only removes the organizational tag.

Server Naming Best Practices

In addition to labels, consider adopting a meaningful server naming convention:

[environment]-[project]-[role]-[number]

Examples:

prod-alpha-web-01
staging-beta-db-01
dev-internal-worker-01

Combine descriptive names with labels for maximum clarity. You can change the server display name from the Settings tab — see Changing Your Server Hostname.

Tips for Effective Organization

Define your labeling system early — Before deploying many servers, agree on a standard set of label categories with your team.

Be consistent — Use the same labels across all servers. Avoid synonyms (e.g., do not use both prod and production).

Keep it simple — Start with 2 to 4 label categories. You can always add more later.

Document your labels — Maintain a reference document listing all labels and their meanings so team members use them consistently.

Review periodically — As projects end or servers are repurposed, update labels to reflect current usage.

What to Do Next

Understanding Your Server Dashboard — Explore all dashboard features.
Viewing Server Activity Log — Track changes to your servers.
Managing Your Team Members — Collaborate with your team.
Changing Your Server Hostname — Set meaningful server names.

Was this article helpful?

← Back to Server Management Browse all categories →

Still have questions?

Contact Support →Submit a Ticket