Public bug reported:
When a user requests non-existing resource or a bad parameter, neutron API
module logs it as TRACE level (log.exception). It is so annoying for debugging
or log monitoring. These kinds of events are usual behaviors and are not errors
of neutron-server.
They should be logged as TRACE level. Errors mapped into 4xx HTTP response are
categorized into this category.
** Affects: neutron
Importance: Medium
Assignee: Akihiro Motoki (amotoki)
Status: In Progress
** Tags: neutron-core
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1282394
Title:
Exceptions due to bad user requests should not be logged as TRACE
Status in OpenStack Neutron (virtual network service):
In Progress
Bug description:
When a user requests non-existing resource or a bad parameter, neutron API
module logs it as TRACE level (log.exception). It is so annoying for debugging
or log monitoring. These kinds of events are usual behaviors and are not errors
of neutron-server.
They should be logged as TRACE level. Errors mapped into 4xx HTTP response
are categorized into this category.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1282394/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
