| 2015-12-31 12:07:01 |
Éric Lemoine |
description |
Heka logstreamer stores journal files /var/cache/lma_collector/logstreamer. This is what the directory looks like on my controller node:
# ls /var/cache/lma_collector/logstreamer/
keystone-wsgi-admin mysql ovsdb-server pacemaker rabbitmq.node-10-sasl system.cron.log system.debug system.kern.log system.syslog
keystone-wsgi-main openstack.swift ovs-vswitchd rabbitmq.node-10 system.auth.log system.daemon.log system.haproxy.log system.messages
There are no journal files for openstack.nova, openstack.neutron, etc. I.e. for all the OpenStack logs handled by the "openstack_log.lua" decoder sandbox. (Note that there IS a journal file for openstack.swift, which is handled by another decoder.)
This is a big issue, as it means that the all the logs are reprocessed when the LMA service is restarted! |
Heka logstreamer stores journal files in /var/cache/lma_collector/logstreamer. This is what the directory looks like on my controller node:
# ls /var/cache/lma_collector/logstreamer/
keystone-wsgi-admin mysql ovsdb-server pacemaker rabbitmq.node-10-sasl system.cron.log system.debug system.kern.log system.syslog
keystone-wsgi-main openstack.swift ovs-vswitchd rabbitmq.node-10 system.auth.log system.daemon.log system.haproxy.log system.messages
There are no journal files for openstack.nova, openstack.neutron, etc. I.e. for all the OpenStack logs handled by the "openstack_log.lua" decoder sandbox. (Note that there IS a journal file for openstack.swift, which is handled by another decoder.)
This is a big issue, as it means that the all the logs are reprocessed when the LMA service is restarted! |
|
