Machine Monitoring and Workspaces

Support, Troubleshooting, & Help
,
1

Hi all,

I’m looking to get some info. The configuration that goes into Machine Monitoring (Machines, Types, Data Sources, etc.)

image
image702×388 16.4 KB

This is shared across all workspaces in an instance? Or is it only certain things that get shared between them?

Is there any way to separate this or to enforce one workspace isn’t able to access anothers?

Thanks,
Darin

2

Hi Darin,

Yes, that’s correct. Machine Monitoring configuration (Machines, Machine Types, Attributes, Activity Fields, States, Downtime Reasons, and Data Sources) is shared across all workspaces within the same Tulip instance. These are instance-wide/global resources, not workspace-scoped.

There isn’t currently a way to isolate or restrict Machine Monitoring objects by workspace. All workspaces in an instance can see and use the same Machine Monitoring configuration.

If separation is required, the typical approaches are:

  1. Naming conventions – Use clear prefixes or suffixes to distinguish machines/configs by workspace (e.g., “WS1_Machine01”, “WS2_Machine01”)

  2. Separate instances – For strict isolation requirements, using different Tulip instances is the recommended approach

Let me know if you’d like recommendations for structuring this cleanly across teams!