It would be fantastic if we could multihome agents to various workspaces.
Right now we use the SCOM agent to connect to OMS, which means one OMS workspace. But we would like to have multiple workspaces depending on type of server (eg Production servers, Dev servers, application servers etc).
I understand we can multihome OMS to different workspaces by multihoming the SCOM agent to different SCOM management groups, but having an entire management group set up just so agents can talk to different OMS workspaces is like swatting a fly with a sledgehammer.
Even if we can manually configure each agent to different OMS workspaces would be fine.
How hard would this be to implement?
We support multi-homing for Windows agents:
We are working on multihoming for Linux agents.
We are also working on support for multihoming with the Azure VM extension
Multi homing blog post link from OMS Log Analytics Team is dead.
Karishma Tiwari commented
@OMS Log Analytics Team (Admin, Microsoft Azure)
Do we have an ETA on Workspace multi-homing support with Azure Log Analytics Extension for VMs?
Daniel Jefferies commented
I'm a director of product working on a marketplace offering that is capable of delivering metrics to multiple OMS workspaces.
The preview is focused on AWS endpoints but coming iterations will add a variety of datacenter endpoints as well.
I'd love your feedback on this product as a potential solution for delivering data to multiple OMS workspaces.
If you are interested in providing feedback, please contact me at firstname.lastname@example.org
Steven Neville commented
Is multihoming configurable via azure ARM templates? I know it's possible to setup one OMS workspace but I haven't found a way to do multihomed setups yet.