Event load balancers
- Juan Tomás Alonso Nieto (Deactivated)
- Julio Vargas
- Former user (Deleted)
- Borja Moro Moreno
Overview
In order to send data to Devo, you need to send the information to an Event load balancer (ELB). The ELB will balance the load among the different data nodes in your Devo deployment. Data sources able to properly tag their events can use this method to send their events directly to Devo.
You can check the available ELB endpoints associated with your Devo deployment in Administration → Relays and ELBs → Event load balancers (ELBs).
What permissions do I need?
To access this area to manage ELBs, you need to have the Manage versión of the Relays and ELBs permission. Having the View version will not allow any task other than just check them.
Types of ELBs
There are two different types of ELBs:
syslog ELB | You can use this ELB to send your events directly to Devo using the syslog protocol. To do it, you have to use TLS client auth using your domain certificate. Click the ellipsis icon and select Download the certificate to get the required certificates. You will be taken to the Administration → Credentials → X.509 Certificates screen, where you must download the certificate, private key, and chain. Learn more about X.509 certificates in this article. |
|---|---|
HTTP ELB | You can send your events to Devo using an HTTP endpoint. To authorize the process, you must generate a token in Devo, and then send the HTTP request to the required endpoint according to your region. Click the ellipsis icon and select Tokens Http/Apiv2 to generate the required token. You'll be taken to the Administration → Credentials → Authentication tokens, where you can create the required token. Check the available HTTP endpoints and instructions to generate the required token and send the events in this article. |
In case you need some additional ELBs for your domain, use our support site to contact us.
Note that for TLS 1.2, the following cipher suites are not allowed:
TLS_RSA_WITH_AES_256_CBC_SHA256TLS_RSA_WITH_AES_128_CCMTLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256TLS_RSA_WITH_AES_256_GCM_SHA384TLS_RSA_WITH_AES_128_CBC_SHA256TLS_RSA_WITH_AES_128_GCM_SHA256TLS_RSA_WITH_AES_256_CCMTLS_ECDHE_RSA_WITH_ARIA_128_GCM_SHA256TLS_RSA_WITH_ARIA_128_GCM_SHA256TLS_RSA_WITH_ARIA_256_GCM_SHA384TLS_RSA_WITH_AES_256_CCM_8TLS_ECDHE_RSA_WITH_AES_128_CBC_SHATLS_ECDHE_RSA_WITH_ARIA_256_GCM_SHA384TLS_RSA_WITH_AES_128_CCM_8TLS_RSA_WITH_AES_128_CBC_SHATLS_ECDHE_RSA_WITH_AES_256_CBC_SHATLS_RSA_WITH_AES_256_CBC_SHA