Set up your network devices so they send network data to New Relic One.
Prerequisites and supported SNMP versions
- A New Relic account. Don't have one? Sign up for free! No credit card required.
- A New Relic account ID.
- A New Relic license key.
- Docker installed in a Linux host.
- SSH access to the Docker host, with the ability to launch new containers.
Direction | Source | Destination | Ports | Protocol |
---|---|---|---|---|
Outbound | Docker host | [ | 443 | TCP |
Outbound | Docker host | New Relic Metric
API
US Endpoint: | 443 | TCP |
Outbound | Docker host | New Relic Log
API
US Endpoint: | 443 | TCP |
Outbound | Docker host | Target devices for SNMP polling | 161 (default) | UDP |
Inbound | Source devices for SNMP Trap data | Docker host | 162 (default) | UDP |
Our NPM container supports all major versions of SNMP (v1, v2c, and v3). Additionally, SNMP v3 has support for the following authentication and privacy settings:
Setting | Protocol |
---|---|
Authentication |
|
Authentication |
|
Authentication |
|
Authentication |
|
Authentication |
|
Authentication |
|
Authentication |
|
Privacy |
|
Privacy |
|
Privacy |
|
Privacy |
|
Privacy |
|
Privacy |
|
Privacy |
|
ヒント
We recommend using read-only community strings/authentication with SNMP.
Set up SNMP data monitoring in New Relic One
- Go to one.newrelic.com and click Add more data.
- Scroll down until you see Network performance monitoring and click SNMP.
- Follow the steps in New Relic One.
one.newrelic.com > Add more data > Network performance monitoring > SNMP to set up SNMP data monitoring. - To get better visibility into how your network is being used, set up network flow data monitoring.
- Visualize your network performance data in New Relic.
If you prefer to do the setup manually, proceed with the following steps.
On a Linux host with Docker installed, download the ktranslate image by running one of the following:
- Docker Hubbash$docker pull kentik/ktranslate:v2
- Quay.iobash$docker pull quay.io/kentik/ktranslate:v2
- Docker Hub
Copy the
snmp-base.yaml
file to the local$HOME
directory of your Docker user, and discard the container by runningbash$cd .$id=$(docker create kentik/ktranslate:v2)$docker cp $id:/etc/ktranslate/snmp-base.yaml .$docker rm -v $idEdit the
snmp-base.yaml
file and define thediscovery.cidrs
anddiscovery.default_communities
attributes to appropriate values for your network.ヒント
We recommend to set
discovery.add_mibs: true
to automate the addition of all discovered MIBs into theglobal.mibs_enabled
attribute.Launch a short-lived container to execute discovery by running
bash$docker run -ti --name ktranslate-discovery --rm --net=host \>--user `id -u`:`id -g` \>-v `pwd`/snmp-base.yaml:/snmp-base.yaml \>kentik/ktranslate:v2 \>-snmp /snmp-base.yaml \>-log_level info \>-snmp_discovery=trueAfter the discovery run finishes, you should see an output similar to the following:
bash$>[Info] KTranslate Adding 3 new snmp devices to the config, 0 replaced from 3$# In this example, the discovery run found 3 new SNMP devices.The discovered devices are listed in the
snmp-base.yaml
file'sdevices.{}
section. By default, only theIF-MIB
mib is polled. You can manually add other mibs to theglobal.mibs_enabled
attribute if you did not setdiscovery.add_mibs: true
before running the discovery.Run
ktranslate
to poll target devices by running:bash$docker run -d --name ktranslate-snmp --restart unless-stopped --net=host \>-v `pwd`/snmp-base.yaml:/snmp-base.yaml \>-e NEW_RELIC_API_KEY=$YOUR_NR_LICENSE_KEY \>kentik/ktranslate:v2 \>-snmp /snmp-base.yaml \>-nr_account_id=$YOUR_NR_ACCOUNT_ID \>## If your account is located in Europe, add the following flag:$## -nr_region=EU \$## If you want to use FedRAMP, add the following flag to use the FedRAMP authorized endpoints:$## -nr_region=GOV \$-metrics=jchf \>-tee_logs=true \>-service_name=snmp \>nr1.snmpTo get better visibility into how your network is being used, set up network flow data monitoring.
To get insights into system messages from your devices, setup network syslog collection.