Your organization does not currently have an active maintenance agreement. Please contact Netuitive Sales for further assistance.

Linux Agent

Using the Linux Agent, you can quickly deploy and collect metrics with a rich set of metadata.

The agent discovers and collects KPI metrics, integrates with CloudWatch, and can leverage other agent metrics. Using various plugins, the Linux Agent can also pull metrics from many different products running on a Linux operating system (in addition to pulling metrics from the host Linux OS).

Dependencies

OS Linux Agent
  • Redhat 6 and 7
  • CentOS 6 and 7
  • Amazon Linux (latest)
  • Ubuntu 12, 14, 15, and 16
  • Debian 7, 8, and 9
  • CPU: /proc/stat
  • Diskspace: /proc/mounts
  • Disk Usage: /proc/diskstats
  • Load Average: /proc/loadavg
  • Memory: /proc/stat
  • Network: /proc/net/dev
  • VM Stat: /proc/vmstat
 
 

Upgrading the Linux Agent 

  1. Stop the Linux Agent (use the appropriate command for your distro). The most common being:
    • service netuitive-agent stop
    • /etc/init.d/netuitive-agent stop
    • initctl stop netuitive-agent
    • systemctl stop netuitive-agent
  2. Run the update command for your distro:
    • yum -y update netuitive-agent
    • apt-get update netuitive-agent
    • apt-get install --only-upgrade netuitive-agent

      If you have not customized the Netuitive configuration file in any way (other than inputting the API key), jump to step 6. If you’ve customized the configuration file, continue on.

  3.  Get the difference between the old configuration file (netuitive-agent.conf) and the new configuration file (netuitive-agent.conf.rpmnew):
    diff -u /opt/netuitive-agent/conf/netuitive-agent.conf.rpmnew /opt/netuitiveagent/conf/netuitive-agent.conf
  4. Copy your changes from the old file to new file.
  5. Rename the old file to netuitive-agent.conf.old and the new configuration file to netuitive-agent.conf.
  6. Start the Linux Agent. The most common commands being:
    • service netuitive-agent start
    • /etc/init.d/netuitive-agent start
    • initctl start netuitive-agent
    • systemctl start netuitive-agent

Standard Installation 

Get Command From Linux Integration Setup Page

  1. From the top navigation menu, select Integrations.
  2. Select the Linux card. The name should be already populated, and Data Collection should be enabled.
  3. Highlight the one-line install command from the instructions and copy them. A unique API key for your account has already been generated and included in the command line.

Specifying the Element Name

If you’d prefer to specify the element name, copy the following instead:

sudo N_APIKEY=your-apikey N_HOSTNAME=your-element-name bash -c "$(curl -Ls http://repos.app.netuitive.com/linux.sh)"

your-apikey is the API key generated from the integration and your-element-name can be any element name you wish (it must be unique from your other elements).

Install Linux Agent 

Paste the command from the previous section into your command line. This installs the agent and adds your account’s unique API key to the configuration file. Prefer to install manually? See our Manual Installation page. 

If you install our Linux Agent on an AWS EC2 or Azure VM, the EC2’s / VM’s power state (it will come in as the attribute hostRunning with a value of true or false) and tags are copied over to the corresponding Linux SERVER element. You can then use this information to create policies.

Edit Linux Agent Config File

  1. Navigate to the Linux Agent configuration file found at <b>/opt/netuitive-agent/conf/netuitive-agent.conf</b>.
  2. Ensure the API key provided in step 1 is input in the netuitive-agent.conf file. The section below is only a portion of the config file. Go here to view the full config file.
     [[NetuitiveHandler]]
        ### MetriclyCloud URL to post the metrics
        url = https://api.app.metricly.com/ingest/infrastructure
    
        ## Metricly Datasource api key
        api_key = 
    
        ### Uncomment to add tags (optional)
        # tags = tag1:tag1val, tag2:tag2val
    
        ### Uncomment to add relations
        # relations = element1, element2
    
        # How many samples to store before sending to Metricly
        batch = 100
    
        # how many batches to store before trimming
        max_backlog_multiplier = 5
    
        # Trim down how many batches
        trim_backlog_multiplier = 4
    
        # local statsd server
        [[[statsd]]]
        enabled = False
     
     
  3. Options:
    • Tags:  Substitute tags value with desired tags and uncomment the line to pass in tags for your element.
    • Relations:  Substitute relations value with desired element relationships; must include the fully qualified name of the elements. Uncomment the line to pass in relationships for your element.
    • Collectors: Adjust  default collectors (CPU, DiskSpace, DiskUsage, Heartbeat, LoadAverage, Memory, VMStat, Network) using the configuration options found here.
  4. Save your file.
  5. Restart the Linux Agent service to begin monitoring your data with Metricly.

This integration’s package (computed metrics, dashboards, and policies that will give you important events and alerts) will be automatically enabled and provisioned to your account as soon as Metricly receives data from the integration.

The PACKAGES button on the integration setup page will become active once data is received, so you’ll be able to disable and re-enable the package at will.

Common Commands

  • service netuitive-agent {stop|start|restart}
  • /etc/init.d/netuitive-agent {stop|start|restart}
  • initctl {stop|start|restart} netuitive-agent
  • systemctl {stop|start|restart} netuitive-agent

Debug  

You can put the agent in Debug mode by changing the logger_root section of the configuration file from INFO to DEBUG. You can also review our chapter on troubleshooting for more information on debugging.

Have more questions? Submit a request

Comments

Powered by Zendesk