a20481631d
* fix the logic of adding omsagent user to secondary group
* remove omsagent user from primary group of omiusers during uninstall
* Revert "remove omsagent user from primary group of omiusers during uninstall"
This reverts commit
|
||
---|---|---|
.github/workflows | ||
build | ||
docs | ||
installer | ||
source | ||
test | ||
tools | ||
.gitignore | ||
.gitmodules | ||
CONTRIBUTING.md | ||
Dockerfile | ||
LICENSE | ||
README.md | ||
SECURITY.md | ||
cgmanifest.json |
README.md
Operations Management Suite Agent for Linux
Overview
Welcome to the Log Analytics agent for Linux! The agent for Linux enables rich and real-time analytics for operational data (Syslog, performance, alerts, inventory) from Linux servers, Docker containers and monitoring tools like Nagios, Zabbix and System Center.
⚠️ The Log Analytics agent is on a deprecation path and won't be supported after August 31, 2024. If you use the Log Analytics agent to ingest data to Azure Monitor, make sure to migrate to the new Azure Monitor agent prior to that date.
Quick Install guide
The following steps configure setup of the Log Analytics agent in Azure and Azure Government cloud. Commands are for 64-bit. Before installing the Log Analytics agent for Linux, you need the workspace ID and key for your Azure Monitor Log Analytics workspace.
- In the Azure portal, click All services found in the upper left-hand corner. In the list of resources, type Log Analytics Workspace. As you begin typing, the list filters based on your input. Select Log Analytics Workspace.
- In your list of Log Analytics workspaces, select the workspace.
- Select Agents Management from the left hand pane.
- Select the Linux Servers tab.
- There is a dropdown chevron next to Log Analytics agent instructions. Click it.
- Copy and paste into your favorite editor the value to the right of Workspace ID and Primary Key.
To configure the Linux computer to connect to an Azure Monitor Log Analytics workspace, run the following command providing the workspace ID and primary key copied earlier. The following command downloads the agent, validates its checksum, and installs it.
For Azure Monitor Log Analytics workspace in commercial cloud:
wget https://raw.githubusercontent.com/Microsoft/OMS-Agent-for-Linux/master/installer/scripts/onboard_agent.sh && sh onboard_agent.sh -w <YOUR WORKSPACE ID> -s <YOUR WORKSPACE PRIMARY KEY>
For Azure Monitor Log Analytics workspace in Azure Government cloud:
wget https://raw.githubusercontent.com/Microsoft/OMS-Agent-for-Linux/master/installer/scripts/onboard_agent.sh && sh onboard_agent.sh -w <YOUR WORKSPACE ID> -s <YOUR WORKSPACE PRIMARY KEY> -d opinsights.azure.us
Azure Install guide
If you are an Azure customer, we have an Azure VM extension that allows you to easily onboard to Azure Monitor Log Analytics workspace.
Full installation guide
Download Latest OMS Agent for Linux (64-bit)
Download Latest OMS Agent for Linux (Final 32-bit Release)
Feedback
We love feedback! Whether it be good, bad or indifferent, it really helps us build a better product for you. There are a few different routes to give feedback:
- UserVoice: Post ideas for new Azure Monitor logs features to work on here
- Monthly survey: if you are an Azure Monitor customer, you know we send out a survey every month asking our customers about the features we’re working on next.
- Elite Linux customer panel: If you are a die-hard Azure Monitor Linux user and want to join our weekly calls and talk directly to the product team apply through this survey.
Supported Linux Operating Systems
Supported Distro/Version strategy
The Log Analytics agent for Linux is built to work with Azure Monitor logs, which has a limited scope of scenarios. Our strategy for supporting new distros and versions starting August 2018 is that we will:
- Only support server versions, no client OS versions.
- Focus support on any of the Azure Linux Endorsed distros. Note that there may be some delay between a new distro/version being Azure Linux Endorsed and it being supported for the Log Analytics Linux agent.
- Not support versions that have passed their manufacturer's end-of-support date.
- Always support the latest GA version of a supported distro.
- Only support VM images; containers, even those derived from official distro publishers' images, are not supported.
- Not support new versions of AMI.
- Only support versions that run SSL 1.x by default.
If you are using a distro or version that is not currently supported and doesn't fit our future support strategy, we recommend that you fork this repo, acknowledging that Microsoft support will not provide assistance with for forked agent versions.
Pre-1.13.27 Python Requirements
64-bit
- CentOS 7, and 8
- Amazon Linux 2017.09
- Oracle Linux 7 and 8
- Red Hat Enterprise Linux Server 7, 8 and 9
- Debian GNU/Linux 8, 9, 10, 11
- Ubuntu Linux 14.04 LTS, 16.04 LTS, 18.04 LTS, 20.04 LTS and 22.04 LTS
- SUSE Linux Enterprise Server 12 and 15
- Rocky 8, and 9
- Alma 8, and 9
32-bit
- CentOS 6
- Oracle Linux 6
- Red Hat Enterprise Linux Server 6
- Debian GNU/Linux 8 and 9
- Ubuntu Linux 14.04 LTS and 16.04 LTS
Note: Containers are not supported. If you need to monitor containers, please leverage the Container Monitoring solution for Docker hosts or Azure Monitor for containers for Kubernetes.
Note: Openssl 1.1.0 is only supported on x86_64 platforms (64-bit).
Note: OpenSSL < 1.x is not supported on any platform.
Troubleshooting Guide
Supported Scenarios
-
Heartbeat data collection
-
Syslog data collection
-
Docker collection
-
Performance data collection
-
Nagios and Zabbix alert collection
-
CollectD Metrics Collection
-
Custom JSON Data
-
VMware Monitoring
Code of Conduct
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.