Brief description of argus probe to client topology
Detailed well in a thread in the argus-info mailing list is a good description of why and how you would use radium, and a recommended design strategy.
What you are looking at is very easy:
local argus-> local radium-> remote radium-> local ra* client
Use radium to transmit across network links, then use the ra clients to connect to local radium instances. The developer also recommends rasqlinsert be located on the local DB server, if at all possible.
I assume that radium does some proper buffering, a function not maintained by argus or the other ra* clients, but I am not familiar enough to be confident with this conclusion yet.