Linux MMA agent - Handling dual homing to Azure Monitor

%3CLINGO-SUB%20id%3D%22lingo-sub-388702%22%20slang%3D%22en-US%22%3ELinux%20MMA%20agent%20-%20Handling%20dual%20homing%20to%20Azure%20Monitor%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-388702%22%20slang%3D%22en-US%22%3E%3CP%3ELooking%20for%20guidance%20on%20how%20people%20who%20have%20a%20SCOM%20environment%20are%20adopting%20Azure%20Monitor.%3C%2FP%3E%3CP%3EDue%20to%20the%20lack%20of%20dual%20homing%20support%20for%20the%20Microsoft%20Monitoring%20Agent%20(MMA)%20%2F%20SCOM%20Agent%20it%20seems%20that%20there%20is%20currently%20no%20native%20way%20to%20get%20monitoring%20events%20into%20both%20SCOM%20and%20Azure%20Monitor.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20any%20recommended%20best%20practice%20to%20adopt%20Azure%20Monitor%20for%20Linux%20environments%20when%20SCOM%20is%20being%20used%20on-premise%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Looking for guidance on how people who have a SCOM environment are adopting Azure Monitor.

Due to the lack of dual homing support for the Microsoft Monitoring Agent (MMA) / SCOM Agent it seems that there is currently no native way to get monitoring events into both SCOM and Azure Monitor.

 

Is there any recommended best practice to adopt Azure Monitor for Linux environments when SCOM is being used on-premise?

0 Replies