Skip to main content

Best Practice of Using Tags

Tags are invaluable tools in organizing, filtering, and analyzing resources within your monitoring environment. Implementing effective tag management practices can greatly enhance your monitoring and management capabilities. Follow these best practices to ensure effective tag creation and management in your organization:

Develop a Strategic Approach​

Craft a precise plan outlining how tags should be strategically planned and utilized within your organization. Use the provided tag categories to comprehend tag usage, and subsequently, formulate a tailored tagging strategy that aligns with the unique needs of your organization to enable effective resource filtering and grouping. This strategic approach ensures that tags are purposefully implemented, contributing to a more organized system.

Let us take some examples to understand how you can plan a strategy for tag usage.

  • Server Tags: Identify criteria such as location, function, department, or ownership to label and group servers. Examples: "Production", "Development", "Finance", or "US-West".

  • Application Tags: Associate specific applications or software components with tags. Examples: "CRM", "ERP", "Web Server", or "Database".

  • Environment Tags: Differentiate between development, testing, staging, and production environments.

  • Service Tags: Classify resources based on the services they support. Examples: "Email Service", "File Storage", or "Backup Service."

  • Location Tags: Organize resources based on physical or logical locations, including data centers, regions, branches, or network segments.

  • Criticality Tags: Indicate the importance or criticality level of resources. Examples: "Critical", "High", "Medium", or "Low."

  • Team/Owner Tags: Identify responsible teams or individuals for resources, facilitating communication and collaboration within the organization.

  • Vendor Tags: Associate resources with specific vendors or suppliers for tracking performance or vendor-related issues.

Consistent Naming Conventions​

Establish clear and consistent naming conventions for tags to avoid confusion. Ensure that tag names are intuitive and reflect the purpose or category they represent.

Document Tag Usage Guidelines​

Document guidelines on how tags should be used within your organization. Clearly communicate the purpose of each tag category and the criteria for assignment.

Regular Review and Cleanup​

Conduct regular reviews of existing tags to ensure relevance and accuracy. Remove obsolete or unused tags to maintain a clean and efficient tagging structure.

Avoid Overuse of Tags​

Use tags judiciously to avoid clutter and ensure meaningful categorization. Prioritize essential tags that provide the most valuable insights.

Custom Group Creation​

Collaborate within your teams to understand your organization's unique needs and requirements for grouping monitors. Create custom groups based on these discussions to ensure they align with your organizational structure and monitoring objectives. Ensure you understand the differences between Groups and Tags and design your strategy accordingly. 

Auto-Assign Criteria​

Define clear criteria for auto-assigning groups and tags to monitors during the discovery process. Consider factors such as location, function, department, or ownership to automate the assignment process and ensure monitors are categorized accurately.

Prioritize adding tags during the discovery process to monitors. This ensures that monitors are tagged appropriately right from the start, facilitating better organization and management of resources within the AIOps platform.

Key-Value Tag Preference​

Opt for key-value based tags over simple value tags whenever possible. Key-value tags offer greater flexibility and granularity in categorizing and filtering monitors, leading to more precise monitoring and analysis capabilities.

Instance-Level Tagging​

Identify specific use cases where tagging at the instance level is necessary for granular monitoring and management. Assign tags at the instance level to differentiate between multiple instances of the same resource or to capture instance-specific attributes.

Lowercase Tagging​

Standardize tag formatting by using lowercase letters only. This helps maintain consistency and clarity in tag representation throughout the AIOps platform.

Inclusion of Numbers and Special Characters​

Understand that tags can include numbers and special characters, with the first colon separating the Key and Value components. For Example, If we have a tag as 'env:dev:test', AIOps will consider 'env' as Key and 'dev:test' as Value.

By following these best practices, your organization can harness the full potential of tags in Motadata AIOps, resulting in a well-organized, efficient, and insightful monitoring environment.