Devo
Most recent version: v1.2.0
Last updated
Was this helpful?
Most recent version: v1.2.0
Last updated
Was this helpful?
Onum supports integration with Devo.
Select Devo from the list of Data sink types and click Configuration to start.
Now you need to specify how and where to send the data, and how to establish a connection with Devo.
Enter the basic information for the new Data Sink.
Name*
Enter a name for the new Data Sink.
Description
Optionally, enter a description for the Data Sink.
Tags
Add tags to easily identify your Sink. Hit the Enter key after you define each tag.
Now add the configuration to establish the connection.
Devo Cloud*
Net buffer size
Define the number of bytes allocated for buffering network data during transmission to Devo.
Write timeout (ms)
Enter the number of milliseconds to wait before considering the request a timeout.
Idle timeout
Enter the milliseconds the connection remains open and idle before it is automatically terminated or closed.
Dial timeout
The maximum time (in ms) allowed for establishing a connection before the attempt is aborted.
Connection Time to Live
The maximum duration the connection remains active before it is forcibly closed, regardless of whether it is idle or in use.
Certificate*
This is the predefined TLS certificate.
Private Key*
The private key of the corresponding certificate.
Root CA*
The path containing the CA certificate
Click Finish when complete.
You will see the results in Devo as a column in your my.app table.
When you use this sink in a Pipeline, you can configure the output parameters. This is where you give the message the required format to be processed in Devo.
Uncheck Passthrough to manually format the message:
Type
Output type
The Syslog format to send in: - the original BSD format (RFC3164) - the “new” format (RFC5424)
You must select the incoming fields that correspond to each individual value in order to build the end message in Devo. The fields to configure will differ depending on the Syslog type selected.
Header
Enter the header parameters
Priority* /Severity* & Facility* - the field corresponding to the Priority OR the fields corresponding to the Severity and Facility that will be used to make the Priority field.
Timestamp - the field containing the Timestamp value.
Hostname - the field containing the hostname.
Message
Enter the fields used to build the body of the message
Tag - the field contaning the tag.
ProcId - the incoming field with the process ID.
Content - the field used as the content field.
Decide whether or not to include this Data sink info in the metrics and graphs of the area.
Specify the cloud environment you wish to send your data to (US, EU or CA). For details on the URLs, .
