cannot set spool size?

[sysmonk]

Hi,

Trying the newest log-courier, and i'm not able to set the spool size. I get this error:

# /usr/local/bin/log-courier -config /etc/log-courier.conf -log-to-syslog=true
Configuration error: Option /general/spool size must be int64 or similar

The configuration i use:

{
        "general": {
                "spool size": 1024,
                "spool timeout": 5,
                "log level" : "debug"
        },
        "network": {
                "servers": [ ... ],
                "ssl ca": "...",
                "timeout": 15,
                "reconnect": 10
        },
        "includes": [
                "/etc/log-courier.d/*.conf"
        ]
}

By the way, i liked the ability to set the spool size on the command line, that way i can have different spool sizes based on the server role / hostname when starting the script from init script. Now, i need to have separate configs for different servers :(

[driskell]

Hi

Will get this fixed ASAP.

Regarding cmd line options it made sense to me to keep as much in the config file as possible as it's easier to modify than the init script. When I get around to packaging it'll simplify the init script too and make it something that can be updated on package upgrades and is the same on all installations.

If you've done testing with different spool sizes it'll be good to know what positive/negative effects you've seen too. I've only tweaked it a few times and not seen much difference.

Jason

[sysmonk]

Re the testing with different spool sizes - i didn't do any tests on log-courier, but i tried different values on logstash-forwarder. On servers with 3k+ of log lines per second i found that having bigger (i.e. 4096) values would perform a bit better. At the low values (<1024) if there was some hiccup (i.e. increase from 3k to 10k log lines / s for a few minutes), it would take a while for logstash-forwarder to get back in sync, and with higher values it was faster. No real tests done on performance though.