rsyslog should accumulate on all state machines

Now, digging around this page:
http://www.rsyslog.com/sending-messages-to-a-remote-syslog-server/

Seems to say we could just add another line like either:
:syslogtag, startswith, "juju-" @@ip-10-72-129-222.eu-west-1.compute.internal:6514;LongTagForwardFormat
& @@ip-10-33-183-137.eu-west-1.compute.internal:6514;LongTagForwardFormat

Or
:syslogtag, startswith, "juju-" @@ip-10-72-129-222.eu-west-1.compute.internal:6514;LongTagForwardFormat
:syslogtag, startswith, "juju-" @@ip-10-33-183-137.eu-west-1.compute.internal:6514;LongTagForwardFormat

or something like that. However, I couldn't actually see it logging to 2 machines.

Note that I *did* see it logging to machine-0, so the data is still at least slightly correct.

Note that rsyslog doesn't grab the addresses from the API, either. Instead it just always uses agentConfig.APIAddresses()[0]

Because we updated the code so that config will get updates by polling APIHostPorts and that returns addresses which might even be machine private, we risk having agents end up recording an address that ends up not routable, and we'll lose all the logs for that machine.

I think that is reasonably unlikely, since everytime I've seen it machine-local addresses end up after public addresses. Though it does mean we'll probably forward to the Public address of the API server, rather than the private one.