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.
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).
If you’d prefer to choose a different hostname method, copy the following instead:
sudo N_APIKEY=your-apikey N_HOSTNAME_METHOD=hostname-method bash -c "$(curl -Ls http://repos.app.netuitive.com/linux.sh)"
hostname-method can be a hostname method described on the Optional Config page.
false) and tags are copied over to the corresponding Linux SERVER element. You can then use this information to create policies.
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 = <datasource 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
Save the configuration file.
Restart the Linux Agent service to begin monitoring your data with Metricly.