# Best Practices for Dynatrace instrumentation with Tagging/Detection/Naming

**URL:** <https://community.dynatrace.com/t/best-practices-for-dynatrace-instrumentation-with-tagging-detection-naming/22859>\
**Category:** Open Q&A\
**Tags:** management-zones, services-classic, tagging, process-groups\
**Created:** [January 6, 2020, 3:24pm UTC](https://community.dynatrace.com/t/best-practices-for-dynatrace-instrumentation-with-tagging-detection-naming/22859 "2020-01-06T15:24:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![alok\_gupta1](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@alok\_gupta1](https://community.dynatrace.com/u/alok_gupta1)\
**Post date:** [January 6, 2020, 3:24pm UTC](https://community.dynatrace.com/t/best-practices-for-dynatrace-instrumentation-with-tagging-detection-naming/22859/1 "2020-01-06T15:24:06Z")

</div>

What are the some of the best practices to instrument a new environment with Dynatrace.

I am looking for the sequence for the generally suggested configurations.

In my environment i have multiple process groups, Services running on the **Same host for multiple environments (dev/qa/Stage)**

So in this situation, what are the best practices for instrumentation.

which one should be done first ?

- Host Tagging
- process group Detection
- process group naming
- Create mgmt zones
- service Detection
- service naming

Please suggest

---

<div class="post-metadata">

**Author:** ![yasmeen\_hazy1](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/yasmeen_hazy1/32/4040_2.png) [@yasmeen\_hazy1](https://community.dynatrace.com/u/yasmeen_hazy1)\
**Post date:** [January 6, 2020, 4:16pm UTC](https://community.dynatrace.com/t/best-practices-for-dynatrace-instrumentation-with-tagging-detection-naming/22859/2 "2020-01-06T16:16:29Z")

</div>

There’s no set guideline, this is generally what I do when I make a new deployment:

First of all, host groups should be put on the OneAgents, either during or after deployment. This will make the tagging of hosts, processes and services much easier.

Once RUM data is coming through, configure your application detection rules, and enable additional technologies such as JQuery, Icefaces, etc. This needs to be done early to start the 7 day baseline timeframe started asap.

Service and process group detection and then renaming of entities such as services, processes, user actions, should be done as early as possible to avoid re-configuration when these change, and to avoid changing the baseline. You might want to begin thinking about maintenance zones around this point.

Next I would look for any additional monitoring of technologies that could be enabled, e.g. IBM MQ plugins or Redis deep monitoring, etc.

Then I would decide how you’re going to split the data with tagging, and then create management zones off of these tags.

Then look at additional data to be captured through request attributes, user action/session properties, conversion goals, key user actions, key requests, user tags, masking, etc.

Then you can look at enabling additional features, such as synthetics, log monitoring, etc.

---

<div class="post-metadata">

**Author:** ![michael\_bonner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/michael_bonner/32/36830_2.png) [@michael\_bonner](https://community.dynatrace.com/u/michael_bonner)\
**Post date:** [January 6, 2020, 4:44pm UTC](https://community.dynatrace.com/t/best-practices-for-dynatrace-instrumentation-with-tagging-detection-naming/22859/3 "2020-01-06T16:44:52Z")

</div>

Hi Alok!

Yasmeen is correct with the above statement. There is no set guideline, and is up to each tenant owner around the steps they would like to take. I just wanted to post some basic documentation around this process as well.

> **[Best practices and recommendations for tagging](https://docs.dynatrace.com/docs/manage/tags-and-metadata/basic-concepts/best-practices-and-recommendations-for-tagging)**
>
> Learn when it's recommended to use tags that leverage auto-detected metadata, as well as best practices for enriching Dynatrace monitoring with additional metadata.

For basic documentation around these application detection rule stated, and other utilities; here is our documentation basehub

> **[Welcome to Dynatrace Documentation](https://docs.dynatrace.com/docs)**
>
> Learn all you need to know about Dynatrace—how to get started, how to deploy Dynatrace, how to monitor with Dynatrace, and much more.

-Michael

---

<div class="post-metadata">

**Author:** ![ctturner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/ctturner/32/11883_2.png) [@ctturner](https://community.dynatrace.com/u/ctturner)\
**Post date:** [January 7, 2020, 2:06pm UTC](https://community.dynatrace.com/t/best-practices-for-dynatrace-instrumentation-with-tagging-detection-naming/22859/4 "2020-01-07T14:06:24Z")

</div>

[@Alok G.](https://answers.dynatrace.com/users/15581/view.html) I would suggest taking a look at the following articles. There are great use cases and will give you an insite as it relates to how other organizations have tagged and renamed hosts/processes/services.

Host Tags;

> **[Monitoring Windows Workstations with Dynatrace: An IT helpdesk case study](https://www.dynatrace.com/news/blog/monitoring-windows-workstations-with-dynatrace-an-it-helpdesk-case-study/)**
>
> Learn how one organization has utilized Dynatrace for monitoring their Windows workstations to solve a problem of frequent crashes.

Process Rename: [More Effective AI to Human Interactions with Dynatrace Davis](https://www.dynatrace.com/news/blog/more-effective-ai-to-human-interactions-with-dynatrace-davis-at-nycm/)

Markdown Tiles:

> **[Unleash the power of the Dynatrace Markdown Dashboard Tile](https://www.dynatrace.com/news/blog/unleash-the-power-of-the-dynatrace-markdown-dashboard-tile/)**
>
> We recently introduced Markdown to Dynatrace Dashboards. A customer shares some use cases of how they are utilizing the capability.

Auto Tags:

> **[Dynatrace Blog](https://www.dynatrace.com/news/blog/)**
>
> Stay updated on the latest news on observability, automation, AI, and app security. Look here for actionable insights for optimizing your digital ecosystem.

---

<div class="post-metadata">

**Author:** ![alok\_gupta1](https://avatars.discourse-cdn.com/v4/letter/a/94ad74/32.png) [@alok\_gupta1](https://community.dynatrace.com/u/alok_gupta1)\
**Post date:** [January 7, 2020, 5:54pm UTC](https://community.dynatrace.com/t/best-practices-for-dynatrace-instrumentation-with-tagging-detection-naming/22859/5 "2020-01-07T17:54:53Z")

</div>

Thanks much for the valuable suggestions
