--- name: monitoring-agent_linux_1 title: Deploying the agent on a Linux host with no public access description: After you provision an instance of the IBM Cloud Monitoring service in the IBM Cloud, you can deploy the Monitoring agent on your Linux hosts to collect data and metrics automatically. You can configure which metrics to monitor in each environment. last-updated: 2025-02-27 --- > ## Documentation Index > The table of contents for this documentation set is at https://cloud.ibm.com/docs/monitoring?format=markdown > The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt > Use these files to discover more information as needed. # Deploying the agent on a Linux host with no public access {: #agent_linux_1} After you provision an instance of the IBM Cloud Monitoring service in the IBM Cloud, you can deploy the Monitoring agent on your Linux hosts to collect data and metrics automatically. You can configure which metrics to monitor in each environment. {: shortdesc} You can associate one or more tags to each monitoring agent. Tags are comma-separated values that are formatted as **TAG_NAME:TAG_VALUE**. When you monitor your environment, you can use these tags to identify metrics that are available from an agent. For example, you can include information about the service name and location with all of the metrics that are collected by this agent. {: tip} ## Prereqs {: #agent_linux_1_prereqs} Check the topic [Tune Agent](https://docs.sysdig.com/en/docs/installation/configuration/sysdig-agent/tune-agent/){: external} ## Deploying the agent {: #agent_linux_1_deploy_1} Follow these steps if your bare metal or VM is running on the IBM Cloud private network and does not have access to the public sites. Complete the following steps to configure a monitoring agent on Linux to collect and forward metrics to an instance of the IBM Cloud Monitoring service: 1. [Obtain the access key](https://cloud.ibm.com/docs/monitoring?topic=monitoring-access_key&format=markdown#access_key_ibm_cloud_ui). 2. Obtain the private ingestion URL. For more information, see [collector endpoints](https://cloud.ibm.com/docs/monitoring?topic=monitoring-endpoints&format=markdown#endpoints_ingestion). 3. Check that you can reach the repo `http://mirrors.service.networklayer.com/sysdig/`. Whether you have a Bare metal or a Classic VSI, by default you get access to the repo. However, if you have attached a firewall such as vyatta to your server, you must allow traffic through to the subnets listed for your data center in [SSL VPN network (on backend/private network)](https://cloud.ibm.com/hardware-firewall-dedicated?topic=hardware-firewall-dedicated-ibm-cloud-ip-ranges#back-end-private-network). Make sure that you allow all ports, both directions for UDP/TCP/ICMP in your data center. 4. Install the kernel headers. When you install a monitoring agent, the agent uses kernel header files. [Learn more](https://docs.sysdig.com/en/sysdig-secure/install-agent-components/troubleshooting/kernel-header-troubleshooting/){: external} Choose a distribution and run the following command for that distribution. For Debian and Ubuntu Linux distributions, run the following command: ```text apt-get -y install linux-headers-$(uname -r) ``` {: pre} For RHEL, CentOS, and Fedora Linux distributions, run the following command: ```text yum -y install kernel-devel-$(uname -r) ``` {: pre} 5. Configure the repository. For Debian and Ubuntu Linux distributions, run the following commands: ```text curl -s http://mirrors.service.networklayer.com/sysdig/DRAIOS-GPG-KEY.public | apt-key add - ``` {: pre} ```text curl -s -o /etc/apt/sources.list.d/draios.list http://mirrors.service.networklayer.com/sysdig/stable/deb/draios.list ``` {: pre} ```text apt-get update ``` {: pre} For RHEL, CentOS, and Fedora Linux distributions, run the following command: ```text rpm --import http://mirrors.service.networklayer.com/sysdig/DRAIOS-GPG-KEY.public ``` {: pre} ```text curl -s -o /etc/yum.repos.d/draios.repo http://mirrors.service.networklayer.com/sysdig/stable/rpm/draios.repo ``` {: pre} 6. Edit the `draios.repo` file and change the file contents to the following: ```text [draios] name=Draios baseurl=http://mirrors.service.networklayer.com/sysdig/stable/rpm/$basearch enabled=1 gpgcheck=1 gpgkey=http://mirrors.service.networklayer.com/sysdig/DRAIOS-GPG-KEY.public #repo_gpgcheck=1 ``` {: codeblock} 7. Configure the EPEL repository for RHEL, CentOS, and Fedora Linux distributions. Go to the next step if DKMS is available in the distribution. {: note} To verify if DKMS is available, run the following command: For RHEL, CentOS, and Fedora Linux distributions, run the following command: ```text yum list dkms ``` {: pre} If DKMS is not installed, run the following commands to install DKMS. ```text yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm yum install dkms ``` {: pre} To configure the EPEL repository, create a file named `/etc/yum.repos.d/epel.repo` with the following content: ```text [epel] name=Extra Packages for Enterprise Linux 7 - $basearch #baseurl=http://download.fedoraproject.org/pub/epel/7/$basearch #baseurl=http://mirrors.service.softlayer.com/fedora-epel/7Server/$basearch baseurl=http://mirrors.service.softlayer.com/fedora-epel/7/$basearch #metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=$basearch failovermethod=priority enabled=1 gpgcheck=0 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7 ``` {: codeblock} 8. Deploy the monitoring agent. This command must be run from a [private endpoint](https://cloud.ibm.com/docs/monitoring?topic=monitoring-endpoints&format=markdown#endpoints_ingestion_private). For example: ```text echo collector: ingest.private.jp-tok.monitoring.cloud.ibm.com >> /opt/draios/etc/dragent.yaml ``` {: pre} For Debian and Ubuntu Linux distributions, run the following commands: ```text apt-get -y install draios-agent ``` {: pre} ```text echo customerid: MONITORING_ACCESS_KEY >> /opt/draios/etc/dragent.yaml ``` {: pre} ```text echo tags: TAG_DATA >> /opt/draios/etc/dragent.yaml ``` {: pre} ```text echo feature: >> /opt/draios/etc/dragent.yaml ``` {: pre} ```text echo " mode: monitor_light" >> /opt/draios/etc/dragent.yaml ``` {: pre} ```text service dragent restart ``` {: pre} For RHEL, CentOS, and Fedora Linux distributions, run the following commands from a terminal: ```text yum -y install draios-agent ``` {: pre} ```text echo customerid: MONITORING_ACCESS_KEY >> /opt/draios/etc/dragent.yaml ``` {: pre} ```text echo tags: TAG_DATA >> /opt/draios/etc/dragent.yaml ``` {: pre} ```text echo feature: >> /opt/draios/etc/dragent.yaml ``` {: pre} ```text echo " mode: monitor_light" >> /opt/draios/etc/dragent.yaml ``` {: pre} ```text sudo systemctl enable dragent ``` {: pre} ```text sudo systemctl start dragent ``` {: pre} Where * MONITORING_ACCESS_KEY is the ingestion key for the instance. * TAG_DATA are comma-separated tags that are formatted as *TAG_NAME:TAG_VALUE*. You can associate one or more tags to your monitoring agent. For example, *role:serviceX,location:us-south*. * Set **sysdig_capture_enabled** to *false* to disable the capture feature. By default is set to *true*. For more information, see [Working with captures](https://cloud.ibm.com/docs/monitoring?topic=monitoring-captures&format=markdown#captures). * Set **secure** to *true* to use SSL with the communication. 9. Check that the monitoring agent is running. Run the following command: ```text ps -ef | grep sysdig ``` {: pre} To see the latest monitoring agent logs, go to the directory `/opt/draios/logs` and check the log file `draios.log`. To look for errors, you can run the following command: ```text grep error /opt/draios/logs/draios.log ``` {: pre} ## Checking the status of an agent by using the CLI {: #agent_linux_1_status} To check the status of an agent, run the following command: ```text service dragent status ``` {: pre}