What are the most common CMDB CI tags you track?

[bobturbot]

We’ve been working with some customers who are trying to get more value out of the Tags module in ServiceNow for their on-prem and cloud infrastructure resources. We have been seeing inconsistent use of Tags with customers focused on different keys/value definitions. Which is expected, everyone will have different approaches, but wanted to ask the community here on how you are handling this:

1. What are the most common tags (keys) you use to organize your CMDB items?

2. Do you see differences between tags for on-prem vs. cloud resources?

3. Why are you using the Tags module the most? Is it for grouping, relationships, or something else (like linking to Business Services)

Any insights or advice would be awesome!

[Dr Atul G- LNG]

Hi @bobturbot 

I have no great answer for this, but my thoughts

1. What are the most common tags (keys) you use to organize your CMDB items?

Atul: Level1 / Level2 / High attention Servers/ Number of Failure / Under Risk 

1. Do you see differences between tags for on-prem vs. cloud resources?

2. Why are you using the Tags module the most? Is it for grouping, relationships, or something else (like linking to Business Services)

Atul : Mainly in my proejct we used for grouping and reporting purpose 

[bobturbot]

Thanks for sharing your thoughts, Atul!

The tags like Level1/Level2, High Attention Servers, and Under Risk sound interesting—could you elaborate a bit on how those are used in your setup? For example, does Level1/Level2 refer to support tiers, priority levels, or something else? And how do you define or update a tag like Under Risk?

Also, it’s interesting that your primary use case is for grouping and reporting. Do you find tags limiting for relationships or linking to Business Services, or was that just not a focus for your project?

[Dr Atul G- LNG]

Hi @bobturbot 

The tags I mentioned were used in the very early stages for our client. Some of them may seem immature, but others have proven to be quite effective with real use cases. I hope these points help you design your own tags as well.

The tags like Level1/Level2, High Attention Servers, and Under Risk sound interesting—could you elaborate a bit on how those are used in your setup?

For example, does Level1/Level2 refer to support tiers, priority levels, or something else? And how do you define or

Atul: Yes, level 1/ Level 2 for support tiers side. 

update a tag like Under Risk?

Atul: We primarily use these tags for our problem records related to servers. Often, certain servers experience frequent failures and either require updates or replacement with new hardware. However, due to budget constraints, the client doesn't take action. As a result, we tag these servers as "Under Risk." This allows us to quickly justify the downtime in our monthly reports by simply referencing the tag on the server.

Also, it’s interesting that your primary use case is for grouping and reporting. Do you find tags limiting for relationships or linking to Business Services, or was that just not a focus for your project?

Atul: No that was not much focus , we were in very initial stage so like above under risk case, we use for reporting as well.

[Dr Atul G- LNG]

The tags like Level1/Level2, High Attention Servers, and Under Risk sound interesting—could you elaborate a bit on how those are used in your setup?

For example, does Level1/Level2 refer to support tiers, priority levels, or something else? And how do you define or

Atul: Yes, level 1/ Level 2 for support tiers side. 

update a tag like Under Risk?

Atul: We primarily use these tags for our problem records related to servers. Often, certain servers experience frequent failures and either require updates or replacement with new hardware. However, due to budget constraints, the client doesn't take action. As a result, we tag these servers as "Under Risk." This allows us to quickly justify the downtime in our monthly reports by simply referencing the tag on the server.

Also, it’s interesting that your primary use case is for grouping and reporting. Do you find tags limiting for relationships or linking to Business Services, or was that just not a focus for your project?

Atul: No that was not much focus , we were in very initial stage so like above under risk case, we use for reporting as well.