Skip to main content

The Devo Relay is a critical feature of Devo that receives inbound events from your data sources and then sends them to your Devo instance with all the tagging and processing rules that make Devo work as fast as it does.   Release 2.15.1 adds automations and new OS support.  The first automation added removes the additional steps to launch the relay after setup.  With this next feature, all certificates will automatically renew 1.5 months before expiration. This is a huge usability improvement and greatly received!  Lastly, support for Ubuntu 24, aka Noble Numbat, and support for Ubuntu 20 has been retired.  Learn more below!

 

 

Table of Contents

 

Enhancements

Automatic activation

The relay is now automatically activated after setup. No need to go to the UI to click on the activation button.

Learn more in our documentation

 

Automatic renewal of Relay Certificates

Relay certificates are now automatically renewed before expiration, yay! One and a half months before the expiration date, the certificate will be automatically renewed.

 

Support for Ubuntu 24

Added support for Ubuntu 24, also known as Noble Numbat. 

  • Please note, you need to upgrade to devo-monitor v2.1.2 as a requirement.

 

Removed support for Ubuntu 20

Support for this outdated version of Ubuntu is discontinued.

Read more in our documentation.

 

Bug Fixes

Source tag capture groups

Bug stopping this tag in rules from working has now been corrected.

Is anyone seeing an issue when moving to this version that its not creating the the following rule files (therefore not opening the port)

rule-13000.pconf

rule-13001.pconf

rule-13002.pconf

 

13000 being the important one thats not working.

I’m sorry I missed this!

Looking into it now!

I’m sorry I missed this!

Looking into it now!

Thanks. One thing I missed this is for the docker version of the relay.

 

I do have this logged in the support portal also.

​@rheselwood Yes, we removed the default ports from the docker version of the relay. They are still available in the Linux packages. Does this have a major impact for you?

The rational behind it is that we would to make those ports visible in the UI too in the future but we didn’t want to make the change in the packages (normally used for production relays) without moving to a major version. 

​@rheselwood Yes, we removed the default ports from the docker version of the relay. They are still available in the Linux packages. Does this have a major impact for you?

The rational behind it is that we would to make those ports visible in the UI too in the future but we didn’t want to make the change in the packages (normally used for production relays) without moving to a major version. 

​@julio.vargas Thanks for responding. We currently use 13000 for our Windows server events.

 

So is port 13000 now available to be mapped manually now? Or will that come in a future version? Just so I know if we need to hold off upgrades.

Are you guys using the dockerized relay? Let me confirm port 13000 can be added via UI. That was the plan indeed

Correct we are!

Terms & ConditionsCookie settings