This question typically applies to Azure Cloud Roles.  For Azure-managed machines, CloudMonix is Azure-context aware of particular environment where it is running in.  Whether the agent is running in a staging slot, a different Azure service or subscription, CloudMonix knows it and will not co-mingle data.  

Generally, when the agent is running in a service that does not match definition screen in CloudMonix, the agent will pause itself and not upload any data to CloudMonix monitoring servers.