Closed ryboe closed 7 years ago
@y0ssar1an
Its definitely configurable in aerospike.conf
We currently only have the critical failures going to console
logging {
# Log file must be an absolute path.
file /var/log/aerospike/aerospike.log {
context any info
}
# Send log messages to stdout
console {
context any critical
}
}
You can modify the log level to info to include all errors
logging {
# Log file must be an absolute path.
file /var/log/aerospike/aerospike.log {
context any info
}
# Send log messages to stdout
console {
context any info
}
}
results:
| => docker logs aerospike
Aug 25 2016 00:06:38 GMT: INFO (as): (as.c:417) <><><><><><><><><><> Aerospike Community Edition build 3.9.1 <><><><><><><><><><>
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) # Aerospike database configuration file.
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272)
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) # This stanza must come first.
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) service {
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) user root
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) group root
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) paxos-single-replica-limit 1 # Number of nodes where the replica count is automatically reduced to 1.
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) pidfile /var/run/aerospike/asd.pid
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) service-threads 4
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) transaction-queues 4
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) transaction-threads-per-queue 4
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) proto-fd-max 15000
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) }
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272)
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) logging {
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272)
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) # Log file must be an absolute path.
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) file /var/log/aerospike/aerospike.log {
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) context any info
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) }
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272)
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) # Send log messages to stdout
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) console {
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) context any info
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) }
Aug 25 2016 00:06:38 GMT: INFO (config): (cfg.c:3272) }
Ok, awesome! Thank you very much for the tip!
It would be nice if everything going into
/var/log/aerospike/aerospike.log
was also logged to stdout. That way I could get the logs by runningdocker logs <name>
.