Skip to main content

Introduction to Tags

Tags serve as powerful metadata that can be assigned to monitors within your monitoring environment. A tag in Motadata AIOps could be a standalone label or a key-value pair that provides additional context and categorization to your infrastructure elements. With Motadata AIOps tags, you can organize, filter, and analyze your resources more efficiently.

Tags are designed to enhance the way you manage and navigate through your monitored environment. By associating tags with different monitors, you can gain a better understanding of the relationships between resources and streamline your monitoring workflows.

Simple Value Tag​

A simple value tag is a label or identifier without an associated value. It is used to categorize monitors based on a specific attribute. Standalone tags are simple and effective for scenarios where the presence or absence of a particular attribute is sufficient for classification. It's important to note that simple value tags are primarily designed for filtering purposes.

Examples:

  • AWS EC2
  • Azure VM
  • vCenter

Key-Value Tag​

A key-value tag consists of a label (key) and an associated value, providing a more detailed and flexible way to categorize resources. Key-value tags allow you to assign specific attributes or properties to your monitors, enabling a more nuanced classification.

Examples:

  • Environment: Development
  • Environment: Production
  • Application: CRM
  • Application: Web Server

This primary distinction with respect to Standalone tags is that while Standalone tags are limited to filtering, Key-Value tags provide the additional capability of both filtering and grouping monitors, enhancing the flexibility and depth of your resource classification within the monitoring environment.

Benefits of Tagging​

Improved Organization​

Tags allow you to organize your monitored resources logically. You can group related resources together, making it easier to locate and manage specific elements within your infrastructure.

Enhanced Visibility​

By assigning tags to your resources, you gain enhanced visibility into the different aspects of your environment. Tags act as a powerful tool for categorization, helping you focus on specific subsets of data during analysis.

Efficient Analysis​

Tags contribute to efficient data analysis by providing a structured way to filter and search for resources. This is especially valuable in large-scale deployments where the ability to narrow down your focus is crucial.

Key Use Cases for Tags​

Tags in Motadata AIOps are versatile and can be applied to various use cases. Let us look into some specific examples of tags that you can create and subsequently use to organise the monitors in your infrastructure:

Server Tags​

  • Use Case 1: Organizing Servers by Function
Tags"Production", "Development", "Finance"
ScenarioAssign tags to monitors based on their primary function, facilitating the quick identification and management of servers within specific functional categories.
  • Use Case 2: Geographic Location
Tags"US-West", "EU-Central", "APAC"
ScenarioUse location tags to organize monitors based on their physical location, making it easy to monitor resources across different geographical regions.

Application Tags​

  • Use Case 3: Application Classification
Tags"CRM", "ERP", "Web Server," "Database"
ScenarioAssociate tags with monitors having applications or software components to categorize and monitor resources based on their role in supporting specific business applications.

Environment Tags​

  • Use Case 4: Differentiating Environments
Tags"Development," "Testing," "Staging," "Production"
ScenarioUse environment tags to differentiate between different stages of the software development lifecycle, enabling tailored monitoring and analysis for each environment.

Service Tags​

  • Use Case 5: Identifying Core Services
Tags"Email Service," "File Storage," "Backup Service"
ScenarioClassify monitors based on the services they support, making it easy to identify and monitor specific services within the IT infrastructure.

Location Tags​

  • Use Case 6: Network Segmentation
Tags"Data Center A," "Branch Office B," "Network Segment 1"
ScenarioOrganize monitors based on their logical or physical location, aiding in monitoring and troubleshooting across different network zones.

Criticality Tags​

  • Use Case 7: Prioritizing Monitoring Efforts
Tags"Critical", "High", "Medium", "Low"
ScenarioAssign criticality tags to indicate the importance of specific resources, enabling IT teams to prioritize monitoring efforts based on criticality levels.

Team/Owner Tags​

  • Use Case 8: Facilitating Ownership and Collaboration
Tags"Team-A", "Team-B", "Individual-Owner"
ScenarioUse team or owner tags to identify the responsible team or individual for a monitor, facilitating communication, collaboration, and accountability within the IT organization.

Vendor Tags​

  • Use Case 9: Vendor-Related Resource Tracking
Tags"Vendor-X", "Supplier-Y"
ScenarioAssociate monitors that belong to specific vendors or suppliers using tags, making it easier to track and monitor the performance of vendor-provided hardware, software, or services.

These use cases demonstrate the versatility of tags in Motadata AIOps, allowing users to customize their monitoring environment based on various criteria for efficient resource management and analysis.

Difference Between Groups and Tags​

Groups​

  • Purpose: Designed to establish logical boundaries across monitors.
  • Structure: Hierarchical, applicable only to monitors.
  • Scalability: Comparatively difficult to manage at scale due to hierarchical nature.
  • Usage: Primarily employed for data-security purposes and Role-Based Access Control.

Tags​

  • Purpose: Tailored for customer-specific use-cases, offering flexibility and customization.
  • Structure: Flat, available for both monitors and instances.
  • Scalability: Easy to scale if managed properly, making them versatile and adaptable.
  • Usage: Serve as the primary building blocks for enabling efficient organization, filtering, and analysis of resources.