Tags being set by a script appear as a manual tag, which means these tags can be deleted by users

[JannickDT_CM]

We are not setting manual tags, we are setting tags in an automated way via scripting but they appear as manual tags in DT.  So this means that our users can delete these manual tags.

Is there a workarround to prevent the deletion of these manual tags being set by scripts?

[AntonPineiro]

Hi,

Can you check Primary Grail fields and tags?

Best regards

[Julius_Loman]

In Dynatrace Classic, you have:

• auto-tags, where you manage the rules, and Dynatrace tags the entities
• manual tags that you set manually in the UI or using API - https://docs.dynatrace.com/docs/shortlink/api-custom-tags-post
• tags that you set using the environment variable DT_TAGS (applies to process) or OneAgent (only applies to host)

In Dynatrace Gen3 you have:

• tags that you set using the environment variable DT_TAGS (applies to process) or OneAgent (only applies to host)
• primary grail tags (grail fields named primary_tags.<tag> for every signal emitted from the source) and also primary fields.

Based on your question, I'm assuming you use the API approach to tag the entities. If you are on Dynatrace SaaS, I suggest changing the approach to the primary_grail tags and maybe also tagging with DT_TAGS / OneAgent if it fits your case (basically entity types).  Manual and automatic tagging will be eventually removed in SaaS, AFAIK tags set using DT_TAGS and OneAgent will not be removed.

Dynatrace Managed has the same tagging functionality as Dynatrace Classic and there are no changes planned.