• globe icon
    en English
    af Afrikaansam Amharicar Arabiczh-CN Chinese (Simplified)nl Dutchen Englishtl Filipinofr Frenchka Georgiande Germanha Hausaig Igboid Indonesianit Italianja Japanesejw Javanesela Latinne Nepalipt Portugueseru Russianso Somalies Spanishsw Swahilith Thaiuk Ukrainianvi Vietnameseyo Yoruba
  • Free Trial

Basic Agent Usage for CentOS

Overview

This page outlines the basic features of the Motadata Agent for CentOS. To install the Motadata Agent, follow the Agent Installation Instructions for CentOs.

Packages are available for 64-bit x86 and Arm v8 architectures. For other architectures, use the source install.

Note: CentOS 6 and above are supported.

Commands

In Agent v6 and v7, the service manager provided by the operating system is responsible for the Agent lifecycle, while other commands must be run through the Agent binary directly. In Agent v5, almost everything is done through the service manager.

Centos 7 And Higher

DESCRIPTION COMMAND
Start Agent as a service sudo systemctl start motadata-agent
Stop Agent running as a service sudo systemctl stop motadata-agent
Restart Agent running as a service sudo systemctl restart motadata-agent
Status of Agent service sudo systemctl status motadata-agent
Status page of running Agent sudo motadata-agent status
Send flare sudo motadata-agent flare
Display command usage sudo motadata-agent --help
Run a check sudo -u dd-agent -- motadata-agent check

Centos 6

DESCRIPTION COMMAND
Start Agent as a service sudo systemctl start motadata-agent
Stop Agent running as a service sudo systemctl stop motadata-agent
Restart Agent running as a service sudo systemctl restart motadata-agent
Status of Agent service sudo systemctl status motadata-agent
Status page of running Agent sudo motadata-agent status
Send flare sudo motadata-agent flare
Display command usage sudo motadata-agent --help
Run a check sudo -u dd-agent -- motadata-agent check

Configuration

The configuration files and folders for the Agent are located in:
- /etc/motadata-agent/motadata.yaml

Configuration files for Integrations:
- /etc/motadata-agent/conf.d/

  • Motadata has over 500 integrations officially listed.
  • Custom integrations are available through the Motadata API.
  • The Agent is open source.
  • Once integrations have been configured, all data is treated the same throughout Motadata, whether it is living in a datacenter or in an online service.

Motadata recommends you update Motadata Agent with every minor and patch release, or, at a minimum, monthly.

Upgrading to a major Motadata Agent version and keeping it updated is the only supported way to get the latest Agent functionality and fixes. The Agent has frequent update releases, though, and managing updates at enterprise scale can be challenging. That doesn’t mean you should wait for major releases before updating. The right update cadence for your organization depends on your infrastructure and your configuration management practices, but aim for monthly.

To update the Motadata Agent core between two minor versions on a given host, run the corresponding install command for your platform.

Motadata Agent release numbering follows SemVer rules.

Agent Guides

The monitor settings interface displays the following details:

Monitor: The name of the devices provisioned after discovery in a network.
IP: The IP address of the devices provisioned after discovery in a network.
Host: The hostname of the device provisioned after discovery, if available. The IP address is displayed in case the hostname is not available.
Groups: The group under which the monitor is categorized
Type: The type of device based on the device type for which the corresponding credential profile is created.
Apps: The application detected in a monitor after discovery
Actions: There are two actions available for each monitor:

  1. Selecting the icon displays permissible actions for the discovery profile.
    • Disable/Enable :
    • On Maintenance:
    • Schedule Maintenance:
    • Metric Settings:
    • Edit:
    • Delete:
  2. Selecting the icon leads to a re-run of a discovery profile that has already run in the past.
×