Content logged to /var/log/upstart

I'm using Ubuntu 14.10 dev and I'm noticing things logged to /var/log/upstart which may not be intended in this way. After deleting all logs and making a reboot I'm getting these things:

alsa-state.log with "alsa-state stop/pre-start, process 1063" and container-detect.log with "container-detect stop/pre-start, process 278".

I'm not sure why a stop/pre-start event is logged as it is very common and doesn't provide very useful information.

console-setup.log with "Loading /etc/console-setup/cached.kmap.gz".

Maybe this could be intended but I'm not so sure about this too.

cryptdisks.log with " ...done.".

This log is incomplete and it looks the missing part is in /var/log/boot.log with " * cryptswap1 (starting).." and " * cryptswap1 (started)...  * Starting early crypto disks...  ". Maybe all content of /var/log/upstart/cryptdisks.log should go into /var/log/boot.log.

mountall.log with "fsck von util-linux 2.20.1
/dev/sda1: sauber, 205747/9199616 Dateien, 16090003/36781311 Blöcke".

This looks more useful but I'm wondering if this shouldn't go better into /var/log/boot.log too.

procps-static-network-up.log and procps-virtual-filesystems.log with "kernel.printk = 4 4 1 7
net.ipv6.conf.all.use_tempaddr = 2
net.ipv6.conf.default.use_tempaddr = 2
kernel.kptr_restrict = 1
fs.protected_hardlinks = 1
fs.protected_symlinks = 1
kernel.sysrq = 176
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.rp_filter = 1
net.ipv4.tcp_syncookies = 1
kernel.yama.ptrace_scope = 1
vm.mmap_min_addr = 65536
kernel.pid_max = 4194303
vm.dirty_background_bytes = 16777216
vm.dirty_bytes = 16777216
vm.dirty_expire_centisecs = 0
vm.dirty_writeback_centisecs = 0
vm.laptop_mode = 1
vm.swappiness = 0
net.ipv4.ip_default_ttl = 255
net.ipv4.tcp_low_latency = 1"

It looks not intended that the same sysctl options are logged in 2 different files. Maybe it is even not intended to create any of these both logs.