in the modern cloud/container/cattle world, it would be super useful if heka supported SRV records in output addresses, so you can just point it to a name instead of keeping tracks of the ports in use.
I can implement it, should be straight forward, but want to know your opinion on that first.
Specifically I would just take what the user configured as address and use it in name for LookupSRV: https://golang.org/pkg/net/#LookupSRV while keeping service and proto empty. That means it support arbitrary names and it's up to the users to follow the RFC 2782 naming.
Hi,
in the modern cloud/container/cattle world, it would be super useful if heka supported SRV records in output addresses, so you can just point it to a name instead of keeping tracks of the ports in use. I can implement it, should be straight forward, but want to know your opinion on that first. Specifically I would just take what the user configured as address and use it in name for LookupSRV: https://golang.org/pkg/net/#LookupSRV while keeping service and proto empty. That means it support arbitrary names and it's up to the users to follow the RFC 2782 naming.