← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 2083760] [NEW] API request is not logged when neutron is run by httpd+mod_wsgi

 

Public bug reported:

When the monolithic neutron-server is used to serve both api and rpc, we
could check access from the clients logged like;

2024-10-05 17:00:25.898 52377 INFO neutron.wsgi [None req-
de46b401-8c2d-4466-b937-3e40c76ef70e 813a38244a2d425883d89d8609ff0877
37d00479190a45ab8835f8b6abcbadac - - default default] 127.0.0.1 "GET
/v2.0/networks HTTP/1.1" status: 200  len: 213 time: 0.8498089

However the same infomation is not longer logged when neutron API is run
by httpd + mod_wsgi .

This makes it quite difficult to debug problems triggered by API call.

NOTE:
Similar logs may be found in apache logs but this does not help really especially because the log does not contain request id and it becomes quite hard when similar requests come in concurrently.

** Affects: neutron
     Importance: Undecided
         Status: New

** Description changed:

  When the monolithic neutron-server is used to serve both api and rpc, we
  could check access from the clients logged like;
  
  2024-10-05 17:00:25.898 52377 INFO neutron.wsgi [None req-
  de46b401-8c2d-4466-b937-3e40c76ef70e 813a38244a2d425883d89d8609ff0877
  37d00479190a45ab8835f8b6abcbadac - - default default] 127.0.0.1 "GET
  /v2.0/networks HTTP/1.1" status: 200  len: 213 time: 0.8498089
  
  However the same infomation is not longer logged when neutron API is run
  by httpd + mod_wsgi .
  
  This makes it quite difficult to debug problems triggered by API call.
+ 
+ NOTE:
+ Similar logs may be found in apache logs but this does not help really especially because the log does not contain request id and it becomes quite hard when similar requests come in concurrently.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2083760

Title:
  API request is not logged when neutron is run by httpd+mod_wsgi

Status in neutron:
  New

Bug description:
  When the monolithic neutron-server is used to serve both api and rpc,
  we could check access from the clients logged like;

  2024-10-05 17:00:25.898 52377 INFO neutron.wsgi [None req-
  de46b401-8c2d-4466-b937-3e40c76ef70e 813a38244a2d425883d89d8609ff0877
  37d00479190a45ab8835f8b6abcbadac - - default default] 127.0.0.1 "GET
  /v2.0/networks HTTP/1.1" status: 200  len: 213 time: 0.8498089

  However the same infomation is not longer logged when neutron API is
  run by httpd + mod_wsgi .

  This makes it quite difficult to debug problems triggered by API call.

  NOTE:
  Similar logs may be found in apache logs but this does not help really especially because the log does not contain request id and it becomes quite hard when similar requests come in concurrently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2083760/+subscriptions