Sending data to Devo
- Juan Tomás Alonso Nieto (Unlicensed)
A typical deployment environment may have hundreds of distributed event sources including business applications, IT network infrastructure resources, and individual PCs and workstations. Along with the customized nature of internal networks, security policies, and the use of proxies, it's not difficult to appreciate the potential for complexity.
Let's start with the two golden rules for sending data correctly to Devo:
- Events must always be sent to the Devo Cloud over a secure channel.
- Events must arrive at the Devo Cloud with an associated tag recognized by Devo.
If an event source is not capable of tagging its events or if it cannot establish a secure outbound channel, then you will likely have to send its events to the Devo Cloud via a Devo In-House Relay.
However, in cases where the source is capable of tagging events and sending them securely, you can send them directly to the Devo Cloud.
The Devo In-House Relay
The Devo Relay sits within your secure network environment—this is why it's often referred to as the "in-house" relay. It can receive events from numerous and varied sources, then forward the events over a secure channel to the Devo Cloud. Rules that you define on the Relay are designed to recognize inbound events; filter out unwanted events; apply the correct Devo tag; then forward the events securely to your Devo Cloud.
Since some data sources are capable of both tagging events and sending them over a secure channel, the Relay is not always necessary. However, it offers additional useful features like the ability to filter out events that you don't need to send to Devo.
Learn more about the Devo Relay.
Event sources
Every data source is unique and so are the procedures for setting them up to send events to the Devo endpoint, whether that's the Devo Relay or the Devo Cloud. For the purposes of providing configuration instructions, we can divide the event sources into several groups:
- Operating systems including Unix-like systems, Windows, and Mac
- Cloud services like Amazon Web Services
- Commercial products
- Custom apps
Learn more about event sources.
Other data collection methods
Because every deployment environment is unique with its own policies and preferred data management tools, we do not restrict you to any single way of sending data. As long as the data is sent securely and with the correct Devo tag, you can choose how you prefer to send the data.
We provide some general guidelines for using some popular open-source and 3rd-party log collection tools, like NXlog, Fluentd, and Logstash.