- The Devo data analytics platform
- Getting started
- Domain administration
-
Sending data to Devo
-
The Devo In-House Relay
- Installing the Devo Relay
- Configuring the In-House Relay
- Relay migration
- Sending SSL/TLS encrypted events to the Devo relay
- Relay troubleshooting tips (v1.4.2)
- Event sources
- Other data collection methods
- Uploading log files
- Devo software
-
The Devo In-House Relay
-
Searching data
- Accessing data tables
-
Building a query
- Data types in Devo
- Build a query in the search window
- Build a query using LINQ
- Working with JSON objects in data tables
- Subqueries
-
Operations reference
-
Aggregation operations
- Average (avg)
- Count (count)
- First (first)
- First not null (nnfirst)
- HyperLogLog++ (hllpp)
- HyperLogLog++ Count Estimation (hllppcount)
- Last (last)
- Last not null (nnlast)
- Maximum (max)
- Median / 2nd quartile / Percentile 50 (median)
- Minimum (min)
- Non-null average (nnavg)
- Non-null standard deviation (biased) (nnstddev)
- Non-null standard deviation (unbiased) (nnustddev)
- Non-null variance (biased) (nnvar)
- Non-null variance (unbiased) (nnuvar)
- Percentile 10 (percentile10)
- Percentile 25 / 1st quartile (percentile25)
- Percentile 5 (percentile5)
- Percentile 75 / 3rd quartile (percentile75)
- Percentile 90 (percentile90)
- Percentile 95 (percentile95)
- Standard deviation (biased) (stddev)
- Standard deviation (unbiased) (ustddev)
- Sum (sum)
- Sum Square (sum2)
- Variance (biased) (var)
- Variance (unbiased) (uvar)
-
Arithmetic group
- Absolute value (abs)
- Addition, sum, plus / Concatenation (add, +)
- Ceiling (ceil)
- Cube root (cbrt)
- Division (div, \)
- Division remainder (rem, %)
- Floor (floor)
- Modulo (mod, %%)
- Multiplication, product (mul, *)
- Power (pow)
- Real division (rdiv, /)
- Rounding (round)
- Sign (signum)
- Square root (sqrt)
- Subtraction, minus / Additive inverse (sub, -)
-
Conversion group
- Duration (duration)
- Format date (formatdate)
- From base16, b16, hex (from16)
- From base64, b64 (from64)
- From UTF8 (fromutf8)
- From Z85, base85 (fromz85)
- Human size (humanSize)
- Make byte array (mkboxar)
- Parse date (parsedate)
- Regular expression, regexp (re)
- Template (template)
- Timestamp (timestamp)
- To base16, b16, hex (to16)
- To base64, b64, hex (to64)
- To BigInt (bigint)
- To boolean (bool)
- To Float (float)
- To image (image)
- To Int (int)
- To IPv4 (ip4)
- To IPv4 net (net4)
- To IPv6 (ip6)
- To IPv6 compatible (compatible)
- To IPv6 mapped (mapped)
- To IPv6 net (net6)
- To IPv6 translated (translated)
- To MAC address (mac)
- To string (str)
- To string (stringify)
- To UTF8 (toutf8)
- To Z85, base85 (toz85)
- Cryptography group
- Date group
- Flow group
- General group
-
Geolocation group
- Coordinates distance (distance)
- Geocoord (geocoord)
- Geographic coordinate system (coordsystem)
- Geohash (geohash)
- Geohash string (geohashstr)
- Geolocated Accuracy Radius with MaxMind GeoIP2 (mm2accuracyradius)
- Geolocated ASN (mmasn)
- Geolocated ASN with MaxMind GeoIP2 (mm2asn)
- Geolocated AS Organization Name with MaxMind GeoIP2 (mm2asorg)
- Geolocated AS owner (mmasowner)
- Geolocated City (mmcity)
- Geolocated City with MaxMind GeoIP2 (mm2city)
- Geolocated Connection Speed (mmspeed)
- Geolocated connection type with MaxMind GeoIP2 (mm2con)
- Geolocated Coordinates (mmcoordinates)
- Geolocated coordinates with MaxMind GeoIP2 (mm2coordinates)
- Geolocated Country (mmcountry)
- Geolocated Country with MaxMind GeoIP2 (mm2country)
- Geolocated ISP (mmisp)
- Geolocated ISP name with MaxMind GeoIP2 (mm2isp)
- Geolocated Latitude (mmlatitude)
- Geolocated Latitude with MaxMind GeoIP2 (mm2latitude)
- Geolocated Level 1 Subdivision with MaxMind GeoIP2 (mm2subdivision1)
- Geolocated Level 2 Subdivision with MaxMind GeoIP2 (mm2subdivision2)
- Geolocated Longitude (mmlongitude)
- Geolocated Longitude with MaxMind GeoIP2 (mm2longitude)
- Geolocated Organization (mmorg)
- Geolocated organization name with MaxMind GeoIP2 (mm2org)
- Geolocated Postal Code (mmpostalcode)
- Geolocated Postal Code with MaxMind GeoIP2 (mm2postalcode)
- Geolocated Region (mmregion)
- Geolocated Region Name (mmregionname)
- ISO-3166-1 Continent Alpha-2 Code (continentalpha2)
- ISO-3166-1 Continent Name (continentname)
- ISO-3166-1 Country Alpha-2 Code (countryalpha2)
- ISO-3166-1 Country Alpha-2 Continent (countrycontinent)
- ISO-3166-1 Country Alpha-3 Code (countryalpha3)
- ISO-3166-1 Country Latitude (countrylatitude)
- ISO-3166-1 Country Longitude (countrylongitude)
- ISO-3166-1 Country Name (countryname)
- Latitude (latitude)
- Latitude and longitude coordinates (latlon)
- Longitude (longitude)
- Parse geocoord format (parsegeo)
- Represent geocoord format (reprgeo)
- Round coordinates (gridlatlon)
- JSON group
- Logic group
-
Mathematical group
- Arc cosine (acos)
- Arc sine (asin)
- Arc tangent (atan)
- Bitwise AND (band, &)
- Bitwise left shift (lshift, <<)
- Bitwise NOT (bnot, ~)
- Bitwise OR (bor, |)
- Bitwise right shift (rshift, >>)
- Bitwise unsigned right shift (urshift, >>>)
- Bitwise XOR (bxor, ^)
- Cosine (cos)
- e (mathematical constant) (e)
- Exponential: base e (exp)
- Hyperbolic cosine (cosh)
- Hyperbolic sine (sinh)
- Hyperbolic tangent (tanh)
- Logarithm: base 2 (log2)
- Logarithm: base 10 (log10)
- Logarithm: natural / arbitrary base (log)
- Pi (mathematical constant) (pi)
- Sine (sin)
- Tangent (tan)
- Meta Analysis group
- Name group
-
Network group
- HTTP Status Description (httpstatusdescription)
- HTTP Status Type (httpstatustype)
- IP Protocol (ipprotocol)
- IP Reputation Score (reputationscore)
- IP Reputation Tags (reputation)
- IPv4 legal use (purpose)
- IPv6 host number (host)
- IPv6 routing number (routing)
- Is IPv4 (ipip4)
- Is Private IPv4 (isprivate)
- Is Public IPv4 (ispublic)
- Squid Black Lists Flags (sbl)
- Order group
-
Packet group
- Ethernet destination MAC address (etherdst)
- Ethernet payload (etherpayload)
- Ethernet source MAC address (ethersrc)
- Ethernet status (etherstatus)
- Ethernet tag (ethertag)
- EtherType (ethertype)
- Has Ethernet frame (hasether)
- Has IPv4 datagram (hasip4)
- Has TCP segment (hastcp)
- Has UDP datagram (hasudp)
- IPv4 destination address (ip4dst)
- IPv4 differentiated services (ip4ds)
- IPv4 explicit congestion notification (ip4ecn)
- IPv4 flags (ip4flags)
- IPv4 fragment offset (ip4fragment)
- IPv4 header checksum (ip4cs)
- IPv4 header length (ip4hl)
- IPv4 identification (ip4ident)
- IPv4 payload (ip4payload)
- IPv4 protocol (ip4proto)
- IPv4 source address (ip4src)
- IPv4 status (ip4status)
- IPv4 time to live (ip4ttl)
- IPv4 total length (ip4len)
- IPv4 type of service (ip4tos)
- TCP ACK (tcpack)
- TCP checksum (tcpcs)
- TCP destination port (tcpdst)
- TCP flags (tcpflags)
- TCP header length (tcphl)
- TCP payload (tcppayload)
- TCP sequence number (tcpseq)
- TCP source port (tcpsrc)
- TCP status (tcpstatus)
- TCP urgent pointer (tcpurg)
- TCP window size (tcpwin)
- UDP checksum (udpcs)
- UDP destination port (udpdst)
- UDP length (udplen)
- UDP payload (udppayload)
- UDP source port (udpsrc)
- UDP status (udpstatus)
- Statistical group
-
String group
- Contains (has, ->)
- Contains - case insensitive (weakhas)
- Contains tokens (toktains)
- Contains tokens - case insensitive (weaktoktains)
- Edit distance: Damerau (damerau)
- Edit distance: Hamming (hamming)
- Edit distance: Levenshtein (levenshtein)
- Edit distance: OSA (osa)
- Ends with (endswith)
- Format number (formatnumber)
- Hostname public suffix (publicsuffix)
- Hostname root domain (rootdomain)
- Hostname root prefix (rootprefix)
- Hostname root suffix (rootsuffix)
- Hostname subdomains (subdomain)
- Hostname top level domain (topleveldomain)
- Is empty (isempty)
- Is in (`in`, <-)
- Is in - case insensitive (weakin)
- Length (length)
- Locate (locate)
- Lower case (lower)
- Matches (matches, ~)
- Peek (peek)
- Replace all (replaceall)
- Replace first (replace)
- Shannon entropy (shannonentropy)
- Split (split)
- Split regexp (splitre)
- Starts with (startswith)
- Substitute (subs)
- Substitute all (subsall)
- Substring (substring)
- Trim both sides (trim)
- Trim the left side (ltrim)
- Trim the right side (rtrim)
- Upper case (upper)
-
Web group
- Absolute URI (absoluteuri)
- Opaque URI (opaqueuri)
- URI authority (uriauthority)
- URI fragment (urifragment)
- URI host (urihost)
- URI path (uripath)
- URI port (uriport)
- URI query (uriquery)
- URI scheme (urischeme)
- URI ssp (urissp)
- URI user (uriuser)
- URL decode (urldecode)
- User Agent Company (uacompany)
- User Agent Company URL (uacompanyurl)
- User Agent Device Icon (uadeviceicon)
- User Agent Device Information URL (uadeviceinfourl)
- User Agent Device Type (uadevicetype)
- User Agent Family (uafamily)
- User Agent Icon (uaicon)
- User Agent Information URL (uainfourl)
- User Agent is Robot (uaisrobot)
- User Agent Name (uaname)
- User Agent OS Company (uaoscompany)
- User Agent OS Company URL (uaoscompanyurl)
- User Agent OS Family (uaosfamily)
- User Agent OS Icon (uaosicon)
- User Agent OS Name (uaosname)
- User Agent OS URL (uaosurl)
- User Agent Type (uatype)
- User Agent URL (uaurl)
- User Agent Version (uaversion)
-
Aggregation operations
-
Working in the search window
-
Generate charts
- Affinity chord diagram
- Availability timeline
- Bipartite chord diagram
- Bubble chart
- Chart aggregation
- Custom date chart aggregation
- Flame graph
- Flat world map by coordinates
- Flat world map by country
- Google animated heat map
- Google area map
- Google heat map
- Graph diagram
- Histogram
- Pew Pew map
- Pie chart
- Pie layered chart
- Punch card
- Robust Random Cut Forest chart
- Sankey diagram
- Scatter plot
- Time heatmap
- Triple exponential chart
- Voronoi treemap
- Data enrichment
- Setting up a data table
- Advanced data operations
- Use case: eCommerce behavior analysis
-
Generate charts
- Managing your queries
- Best practices for data search
- Monitoring tables
-
Parsers and collectors
- About Devo tags
- Special Devo tags and data tables
-
List of Devo parsers
- Business & Consumer
- Cloud technologies
- Databases
- Host and Operating Systems
-
Network and application security
- auth.secureauth
- auth.securenvoy
- av.mcafee
- av.sophos
- box.iptables
- edr.cylance
- edr.fireeye.alerts
- edr.minervalabs.events
- endpoint.symantec
- firewall.checkpoint
- firewall.cisco firepower and vpn.cisco
- firewall.fortinet
- firewall.huawei
- firewall.juniper
- firewall.paloalto
- firewall.pfsense
- firewall.sonicwall
- firewall.sophos
- firewall.sophos.xgfirewall
- firewall.stonegate
- firewall.windows
- mail.proofpoint
- nac.aruba
- network.meraki
- network.versa
- proxy.bluecoat
- proxy.forcepoint
- proxy.squid
- uba.varonis
- vuln.beyondtrust
- vpn.pulsesecure.sa
- Network connectivity
- Web servers
- Technologies supported in CEF syslog format
- Collectors
- Activeboards
-
Dashboards
- Create a new dashboard
-
Working with dashboard widgets
- Availability timeline widget
- Chord diagram widget
- Circle world map widget
- Color key value widget
- Color world map widget
- Column chart widget
- Comparative chart widget
- Funnel widget
- Gauge meter widget
- Google heatmap widget
- Heat calendar widget
- Line chart widget
- Monitoring widget
- Pie chart widget
- Punch card widget
- Sectored pie chart widget
- Table widget
- Time heatmap widget
- Tree diagram widget
- Voronoi tree widget
- Configuring and sharing dashboards
- Alerts and notifications
- Panels
- Applications
- Tools
- Social Intelligence
- API reference
- Release notes
Relay migration
Introduction
The steps described in this article will guide you through the migration process from an old relay version in your machine to the most recent version (v1.4.2)
The process is as follows:
- Install the new relay in the same machine where the old relay is located with exactly the same relay name so the same rules are downloaded for the new one, and force the download of new certificates from the web app. At this point, both relays will be running at the same time.
- Stop the old relay and wait until the new relay takes over and starts processing the data. This process should take a few seconds. If something goes wrong, start the old relay again and check for issues. Contact us if you need support.
- Once the new relay is handling the traffic, remove the old relay from the machine.
Following these steps, data loss will be minimized as much as possible.
New paths
Take into account that the new relay is deployed on a different path. The files that were under /etc/logtrust
and /opt/logtrust
in previous versions are now under the /opt/devo
folder.
New package name
Also, note that the new package name is devo-scoja-relay and the old one is devo-relay.
Getting ready
Before starting the migration process, you must get your relay name. To do it, connect to the relay via SSH and execute the following command:
# cat /etc/logtrust/relay/logtrust.conf
logtrust.services.url = "https://xxx.devo.com/domain/clientrelay.json"
logtrust.services.downloadHomeRelayConfig.url = "https://xxx.devo.com/domain/clientrelay/config"
api.key = "xxxx"
hardware.id = "ubuntu-xenial-migrationtest"
relay.address = "10.0.2.15"
proxy.host = ""
proxy.port = ""
proxy.user = ""
proxy.pass = ""
version = "1.0"
Your relay name is the value of the parameter hardware.id
. Keep it handy as you will need it to configure the new relay.
Migration procedure
The migration procedure is made up of 4 different steps:
- Step 1 - Install the new relay
- Step 2 - Stop the old relay and make sure the new one is handling the data
- Step 3 - Uninstall the old relay
- Step 4 - Install packages for *nix
Step 1 - Install the new relay
Follow these steps to install the new relay in your machine:
Execute the following command in the same machine where your old version is running to install the new version of the Devo relay:
Ubuntu
sudo apt-get install devo-scoja-relay
CentOS / Red Hat
sudo yum install devo-scoja-relay
The relay configuration utility will be launched, where you must specify the relay configuration settings. Check the step-by-step process for configuring the new relay for Ubuntu here (step 4), and go here if you are installing it in Red Hat or CentOS (step 5).
New relay name
The name of the new relay must be exactly the same as the old one. Otherwise, the relay rules will not be downloaded automatically.
New relay configuration
The configuration settings of the new relay must be exactly the same as the old one
Make sure that OpenJDK8 is being used after the package installation. In case several Java versions are installed, select openjdk8.
# update-alternatives --config java There are 2 choices for the alternative java (providing /usr/bin/java). Selection Path Priority Status ------------------------------------------------------------ 0 /usr/lib/jvm/java-9-openjdk-amd64/bin/java 1091 auto mode * 1 /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java 1081 manual mode 2 /usr/lib/jvm/java-9-openjdk-amd64/bin/java 1091 manual mode Press <enter> to keep the current choice[*], or type selection number:
At this point, both relays are working at the same time and you will see two Java processes running. In the following example, PID 5313 is the old relay and PID 10932 is the new one:
# ps aux | grep java | grep -v grep root 5313 0.2 5.2 2786768 184964 ? Sl 04:43 0:48 java -server -Xms200M -Xmx200M -XX:+UseConcMarkSweepGC -classpath :/opt/logtrust/scoja/scoja.jar:/opt/logtrust/scoja/scoja-cc.jar:/opt/logtrust/scoja/scoja-compression.jar:/opt/logtrust/scoja/scoja-rpc.jar:/opt/logtrust/scoja/scoja-beep.jar:/opt/logtrust/scoja/jython.jar -Djava.library.path=/opt/logtrust/scoja -Dorg.scoja.io.posix.provider=org.scoja.io.posix.PosixNative -Dscoja.home=/opt/logtrust/scoja -Dpython.import.site=false org.scoja.server.Scoja -r 5s -G /etc/logtrust/scoja/version1/all-me.conf -j /etc/logtrust/scoja/version1/all-var.conf root 10932 1.3 9.4 4940144 332620 ? Sl 10:50 0:09 java -XX:+UseConcMarkSweepGC -XX:MaxRAMPercentage=70.0 -XX:InitialRAMPercentage=70.0 -classpath /opt/devo/scoja-server/lib/scoja-server-1.5.1.jar:/opt/devo/scoja-server/lib/scoja-client-1.5.1.jar:/opt/devo/scoja-server/lib/scoja-beep-1.4.0.jar:/opt/devo/scoja-server/lib/scoja-rpc-1.4.0.jar:/opt/devo/scoja-server/lib/scoja-compression-1.4.0.jar:/opt/devo/scoja-server/lib/scoja-rpc-xc-1.4.0.jar:/opt/devo/scoja-server/lib/scoja-cc-1.4.0.jar:/opt/devo/scoja-server/lib/jython-standalone-2.7.2b3.jar:/opt/devo/scoja-server/lib/log4j-1.2.17.jar org.scoja.server.Scoja -r 5s -G /opt/devo/scoja-server/conf/all-me.conf -j /opt/devo/scoja-server/conf/all-var.conf
If you don’t see two Java processes running, check
/var/log/scoja.log
for errors. It may be necessary to stop and start the new relay if you have updated the Java version withupdate-alternatives --config java
. Once you check that both Java processes are running, you can continue.- In Devo, go to Administration → Relays. Click the ellipsis icon that appears at the right of your relay when you hover over it and click Edit.
- Then, check the Force Generate New Certificate check box and click Apply configuration to force the creation of the new certificates.
Wait for 2 minutes and check that the following file exists:
/opt/devo/scoja-server/conf/keys/client.jks
# ll /opt/devo/scoja-server/conf/keys/client.jks -rw-r--r-- 1 root root 8075 Oct 13 11:10 /opt/devo/scoja-server/conf/keys/client.jks
You can also check that the rules have been downloaded and are available in the
/opt/devo/scoja-server/conf/rules
# ll /opt/devo/scoja-server/conf/rules total 28 drwxr-xr-x 2 root root 4096 Oct 13 11:10 ./ drwxr-xr-x 4 root root 4096 Oct 13 11:10 ../ -rw-r--r-- 1 root root 147 Oct 13 11:10 rule-13000.pconf -rw-r--r-- 1 root root 176 Oct 13 11:10 rule-13001.pconf -rw-r--r-- 1 root root 175 Oct 13 11:10 rule-13002.pconf -rw-r--r-- 1 root root 227 Oct 13 11:10 rule-13003.pconf -rw-r--r-- 1 root root 107 Oct 13 11:10 target.pconf
After this step, the Devo Scoja Relay will be installed and ready to be used. The relay rules and certificates will be automatically downloaded from the Devo app.
At this point, the ports are still being used by the old version of the relay (PID 5313 in the example below)
# netstat -atunp | grep java tcp6 0 0 :::13000 :::* LISTEN 5313/java tcp6 0 0 :::13001 :::* LISTEN 5313/java tcp6 0 0 :::13002 :::* LISTEN 5313/java tcp6 0 0 :::13003 :::* LISTEN 5313/java tcp6 0 0 127.0.0.1:5140 :::* LISTEN 5313/java tcp6 0 0 10.0.2.15:42188 54.75.255.25:443 ESTABLISHED 5313/java tcp6 0 0 10.0.2.15:42352 54.75.255.25:443 ESTABLISHED 11231/java tcp6 0 0 127.0.0.1:5140 127.0.0.1:48974 ESTABLISHED 5313/java tcp6 0 0 127.0.0.1:5140 127.0.0.1:48978 ESTABLISHED 5313/java tcp6 0 0 127.0.0.1:5140 127.0.0.1:48976 ESTABLISHED 5313/java udp6 0 0 :::12999 :::* 5313/java udp6 0 0 :::13000 :::* 5313/java udp6 0 0 :::13001 :::* 5313/java udp6 0 0 :::13002 :::* 5313/java udp6 0 0 :::13003 :::* 5313/java udp6 0 0 127.0.0.1:5140 :::* 5313/java udp6 0 0 127.0.0.1:5141 :::* 5313/java
Lastly, if you have installed the logtrust-system utility in your machine, you must uninstall it using the following command (it will be reinstalled later)
Ubuntu
sudo apt-get purge logtrust-system
CentOS / Red Hat
sudo yum remove logrust-system
devo-system
Note that the most recent version of the logtrust-system package is called devo-system. This new package will be installed at the end of this process.
Updating devo-monitor
If you have already installed the devo-monitor package, you don't need to uninstall it.
Step 2 - Stop the old relay and make sure the new one is handling the data
Follow these steps to stop your old relay and check that the new one works properly:
Execute the following command to stop the old relay:
sudo service devo-relay stop
Check that the process stopped and there is only a single Java process running now:
# ps aux | grep scoja | grep -v grep root 11231 1.7 9.6 4963516 339012 ? Sl 11:14 0:08 java -XX:+UseConcMarkSweepGC -XX:MaxRAMPercentage=70.0 -XX:InitialRAMPercentage=70.0 -classpath /opt/devo/scoja-server/lib/scoja-server-1.5.1.jar:/opt/devo/scoja-server/lib/scoja-client-1.5.1.jar:/opt/devo/scoja-server/lib/scoja-beep-1.4.0.jar:/opt/devo/scoja-server/lib/scoja-rpc-1.4.0.jar:/opt/devo/scoja-server/lib/scoja-compression-1.4.0.jar:/opt/devo/scoja-server/lib/scoja-rpc-xc-1.4.0.jar:/opt/devo/scoja-server/lib/scoja-cc-1.4.0.jar:/opt/devo/scoja-server/lib/jython-standalone-2.7.2b3.jar:/opt/devo/scoja-server/lib/log4j-1.2.17.jar org.scoja.server.Scoja -r 5s -G /opt/devo/scoja-server/conf/all-me.conf -j /opt/devo/scoja-server/conf/all-var.conf
Wait for one minute and check that the connections to the ports have changed to the new relay (PID 11231 in the example below)
# netstat -atunp | grep java tcp6 0 0 :::13000 :::* LISTEN 11231/java tcp6 0 0 :::13001 :::* LISTEN 11231/java tcp6 0 0 :::13002 :::* LISTEN 11231/java tcp6 0 0 :::13003 :::* LISTEN 11231/java tcp6 0 0 127.0.0.1:5140 :::* LISTEN 11231/java tcp6 0 0 10.0.2.15:42352 54.75.255.25:443 ESTABLISHED 11231/java udp6 0 0 :::12999 :::* 11231/java udp6 0 0 :::13000 :::* 11231/java udp6 0 0 :::13001 :::* 11231/java udp6 0 0 :::13002 :::* 11231/java udp6 0 0 :::13003 :::* 11231/java udp6 0 0 127.0.0.1:5140 :::* 11231/java udp6 0 0 127.0.0.1:5141 :::* 11231/java
If the connections don’t show up and data stops arriving to Devo, start the old relay again with the following command and contact us.
sudo service devo-relay start
Make sure data is still reaching Devo before moving to the next step.
Step 3 - Uninstall the old relay
Execute the following command to uninstall the old relay:
Ubuntu
sudo apt-get purge devo-relay
CentOS / Red Hat
sudo yum remove devo-relay
Step 4 - Install Devo packages for *nix
It is important to monitor the relay machine by sending system and stats data to Devo.
In order to do that, you must install the most recent versions of the devo-system and devo-monitor packages following the steps explained in Installing Devo packages for *nix.
Labels
- latest