If you are trying to use Operations Manager Suite to monitor your Red Hat or CentOS VMs you will probably face following issue if you use “Connect” button on Log Analytics section in Azure:
There are two ways (tested on CentOS but it same behavior on Red Hat) to make it work:
- Disable Diagnostics for VM during creation
- Use connect button on portal.azure.com
- And after some time
And data will appear in OMS Logs.
Pros: That Workspace Connected on Azure Portal
Cons: Disabled Azure Diag (you’ll monitor VM with OMS – so no need)
- Deploy VM with Azure Diag Enabled:
- In order to enable OMS you’ll have to install agent Manually:
If previously you tried to use Connect VM button on Azure Portal and it was Fail: You have to use Disconnect button and wait until operation finished (VM have to be turned on.)
In Putty on VM
$> sha256sum ./omsagent-1.1.0-28.universal.x64.sh
$> sudo sh ./omsagent-1.1.0-28.universal.x64.sh –upgrade -w <YOUR OMS WORKSPACE ID> -s <YOUR OMS WORKSPACE PRIMARY KEY>
- At the End on azure portal in will be listed as Not Connected but monitoring and data in OMS should appear.
Pros But at the end you’ll both OMS data and Azure Diag.
Cons Not Connected in Azure Portal
Both ways should bring OMS Linux
If you deployed VM with Azure Diag Enabled and decided to disable it and use Connect Button in Log Analytics Section of Portal – it will NOT Fail if
You have to remove extension totally by running following commands:
> sudo rpm -e omsconfig > sudo rpm -e omsagent > sudo /opt/microsoft/scx/bin/uninstall
After that you Can use “Connect” feature)
Happy Monitoring 🙂
THE USE OF THE WEBPAGES OF artempro.ru IS ON YOUR OWN RISK. THE INFORMATION IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, COURSE OF DEALING OR USAGE OF TRADE. artempro.ru AG IS NOT LIABLE FOR ANY WARRANTY CLAIMS OR DAMAGES, IRRESPECTIVE OF THE LEGAL CAUSE, WHETHER IN CONTRACT, WARRANTY, FAILURE OF A REMEDY TO ACHIEVE ITS INTENDED OR ESSENTIAL PURPOSES, TORT (INCLUDING NEGLIGENCE), STRICT LIABILITY, INDEMNITY OR ANY OTHER LEGAL THEORY AND IN PARTICULAR SHALL NOT BE LIABLE FOR DAMAGES INCURRED AS A RESULT OF CONSULTATION, ASSISTANCE IN SETTING-UP PROCEDURES, BUSINESS INTERRUPTION OR SOFTWARE DEFECTS, EXCEPT WHERE LIABILITY IS MANDATORY FOR DAMAGES TO PRIVATELY USED PROPERTY OR BECAUSE OF VIOLATION OF CARDINAL CONTRACTUAL OBLIGATIONS OR DUE TO INTENT, GROSS NEGLIGENCE OR FAILURE TO CONFORM TO EXPRESS WARRANTIES. HOWEVER, LIABILITY FOR DAMAGES ARISING FROM THE VIOLATION OF CARDINAL CONTRACTUAL OBLIGATIONS SHALL BE LIMITED TO THE FORESEEABLE DAMAGE NORMALLY COVERED BY A CONTRACT EXCEPT IN CASES OF WILFUL MISCONDUCT OR GROSS NEGLIGENCE.