# Divide Production and Staging data

**URL:** <https://community.dynatrace.com/t/divide-production-and-staging-data/21789>\
**Category:** Open Q&A\
**Tags:** management-zones, tagging, hosts-classic\
**Created:** [September 3, 2019, 1:07pm UTC](https://community.dynatrace.com/t/divide-production-and-staging-data/21789 "2019-09-03T13:07:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![janne\_olkoniem1](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/janne_olkoniem1/32/37380_2.png) [@janne\_olkoniem1](https://community.dynatrace.com/u/janne_olkoniem1)\
**Post date:** [September 3, 2019, 1:07pm UTC](https://community.dynatrace.com/t/divide-production-and-staging-data/21789/1 "2019-09-03T13:07:09Z")

</div>

Hi,

Is the host group setting way to go when we wan’t to divide data coming from production and staging side. The agents are currently under the same environment in Dynatrace managed but we have an issue with the service naming and merging.

Currently the agents don’t have any host\_group defined so the services are merged between production and staging servers. Not sure currently should we start to taggle this with host groups or try to use some metadata in tagging to split the data.

---

<div class="post-metadata">

**Author:** ![skrystosik](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/skrystosik/32/21133_2.png) [@skrystosik](https://community.dynatrace.com/u/skrystosik)\
**Post date:** [September 3, 2019, 1:54pm UTC](https://community.dynatrace.com/t/divide-production-and-staging-data/21789/2 "2019-09-03T13:54:14Z")

</div>

Host group may help for creating rules for management zones, and splitting process groups. Different hosts groups are one of criteria’s to splits process groups into multiple ones. Than you can create management zone for each env and than you can give permissions for users only to particular part of your monitored entities and data related to them.

> **[Management zones (Dynatrace Classic)](https://docs.dynatrace.com/docs/manage/identity-access-management-classic/permission-management/management-zones)**
>
> Learn about management zones concepts, how to define management zones, and how to make the most of them.

Sebastian

---

<div class="post-metadata">

**Author:** ![sia\_h](https://avatars.discourse-cdn.com/v4/letter/s/f14d63/32.png) [@sia\_h](https://community.dynatrace.com/u/sia_h)\
**Post date:** [September 3, 2019, 1:54pm UTC](https://community.dynatrace.com/t/divide-production-and-staging-data/21789/3 "2019-09-03T13:54:58Z")

</div>

Hi Janne,

That is the right way to split the production entities from the staging entities. When the same process group is running in two different host groups, Dynatrace will create one process group for each host group. Consequently, services are also grouped per host group. So you can configure services differently per host group.

In other words, your transactions and metrics will have their own services and process groups for production, and also for for staging.

> **[Organize your environment using host groups](https://docs.dynatrace.com/docs/observe/infrastructure-observability/hosts/configuration/organize-your-environment-using-host-groups)**
>
> Find out how Dynatrace enables you to organize your hosts, processes, and services using host groups.

Sia
