logging for nova

Bug #1262294 reported by Sergey Vasilenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Committed
Low
Bogdan Dobrelya

Bug Description

At this time we have big set of log files:

nova-keystoneclient.middleware.auth_token.log
nova-migrate.versioning.api.log
nova-nova.api.openstack.compute.contrib.volumes.log
nova-nova.api.openstack.compute.extensions.log
nova-nova.api.openstack.extensions.log
nova-nova.api.openstack.log
nova-nova.api.openstack.wsgi.log
nova-nova.ec2.wsgi.server.log
nova-nova.metadata.wsgi.server.log
nova-nova.network.driver.log
nova-nova.osapi_compute.wsgi.server.log
nova-nova.S3.log
nova-nova.scheduler.filter_scheduler.log

And nobody can say which log file using for each of nova component.

I think we should modify log collecting as well as we make for Neutron -- one logfile for one component:

neutron-agent-dhcp.log
neutron-agent-l3.log
neutron-agent-metadata.log
neutron-agent-ovs.log
neutron-server.log

Tags: nova
Changed in fuel:
milestone: none → 4.1
tags: added: nova
description: updated
Changed in fuel:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :
Changed in fuel:
milestone: 4.1 → 5.0
Changed in fuel:
milestone: 5.0 → 5.1
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :
Changed in fuel:
assignee: nobody → Bogdan Dobrelya (bogdando)
status: Triaged → In Progress
Changed in fuel:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.