Remove access log from stderr for @http decorator

Now eventlet.wsgi.Server in "nameko\web\server.py" leave log_output=True
and log=None

So all access log like
127.0.0.1 - * [18/Mar/2017 00:57:12] "GET /health HTTP/1.1" 200 140 0.001000
127.0.0.1 - * [18/Mar/2017 00:57:22] "GET /health HTTP/1.1" 200 140 0.002001
127.0.0.1 - * [18/Mar/2017 00:57:23] "GET /health HTTP/1.1" 200 140 0.001008
fall to stderr...

Inside docker and Kubernetes we send all container logs to stdout/stderr,
and constant flow of non-formatted/unstoppable/non-configurable lines from
health checks - big problem.

Lets explicit configure logger in nameko\web\server.py

    def get_wsgi_server(
...
        return wsgi.Server(
        ..., log=getLogger('wsgi')
        )

As result - good logs
{"asctime": "2017-03-18 01:05:13,662", "msecs": 662.9447937011719,
"levelname": "INFO", "process": 9304, "module": "wsgi", "lineno": 566,
"args": [], "msg": "127.0.0.1 - * [18/Mar/2017 01:05:13] \"GET /health
HTTP/1.1\" 200 140 0.001000", "request_id": null}
{"asctime": "2017-03-18 01:05:14,888", "msecs": 888.3178234100342,
"levelname": "INFO", "process": 9304, "module": "wsgi", "lineno": 566,
"args": [], "msg": "127.0.0.1 - * [18/Mar/2017 01:05:14] \"GET /health
HTTP/1.1\" 200 140 0.001010", "request_id": null}
{"asctime": "2017-03-18 01:05:16,056", "msecs": 56.3197135925293,
"levelname": "INFO", "process": 9304, "module": "wsgi", "lineno": 566,
"args": [], "msg": "127.0.0.1 - * [18/Mar/2017 01:05:16] \"GET /health
HTTP/1.1\" 200 140 0.001000", "request_id": null}

And control via nameko config

...
LOGGING:
  version: 1
...
  loggers:
    wsgi:
      level: INFO
      handlers: [console]
      propagate: False

This would be cool. Would you like to raise a pull request to add it?

···

On Friday, March 17, 2017 at 11:08:45 PM UTC, trex....@gmail.com wrote:

Now eventlet.wsgi.Server in "nameko\web\server.py" leave log_output=True
and log=None

So all access log like
127.0.0.1 - * [18/Mar/2017 00:57:12] "GET /health HTTP/1.1" 200 140
0.001000
127.0.0.1 - * [18/Mar/2017 00:57:22] "GET /health HTTP/1.1" 200 140
0.002001
127.0.0.1 - * [18/Mar/2017 00:57:23] "GET /health HTTP/1.1" 200 140
0.001008
fall to stderr...

Inside docker and Kubernetes we send all container logs to stdout/stderr,
and constant flow of non-formatted/unstoppable/non-configurable lines from
health checks - big problem.

Lets explicit configure logger in nameko\web\server.py

    def get_wsgi_server(
...
        return wsgi.Server(
        ..., log=getLogger('wsgi')
        )

As result - good logs
{"asctime": "2017-03-18 01:05:13,662", "msecs": 662.9447937011719,
"levelname": "INFO", "process": 9304, "module": "wsgi", "lineno": 566,
"args": [], "msg": "127.0.0.1 - * [18/Mar/2017 01:05:13] \"GET /health
HTTP/1.1\" 200 140 0.001000", "request_id": null}
{"asctime": "2017-03-18 01:05:14,888", "msecs": 888.3178234100342,
"levelname": "INFO", "process": 9304, "module": "wsgi", "lineno": 566,
"args": [], "msg": "127.0.0.1 - * [18/Mar/2017 01:05:14] \"GET /health
HTTP/1.1\" 200 140 0.001010", "request_id": null}
{"asctime": "2017-03-18 01:05:16,056", "msecs": 56.3197135925293,
"levelname": "INFO", "process": 9304, "module": "wsgi", "lineno": 566,
"args": [], "msg": "127.0.0.1 - * [18/Mar/2017 01:05:16] \"GET /health
HTTP/1.1\" 200 140 0.001000", "request_id": null}

And control via nameko config

...
LOGGING:
  version: 1
...
  loggers:
    wsgi:
      level: INFO
      handlers: [console]
      propagate: False

This would be cool. Would you like to raise a pull request to add it?

Yes. What i need to do? Or just wait your activity?

···

On Saturday, March 18, 2017 at 1:16:38 PM UTC+2, Matt Yule-Bennett wrote:

Fork the https://github.com/nameko/nameko repo, make your changes in a
branch, and then create a pull request from that branch back to the master
branch on nameko/nameko.

There's a decent guide here:

···

On Saturday, March 18, 2017 at 4:29:30 PM UTC, trex....@gmail.com wrote:

On Saturday, March 18, 2017 at 1:16:38 PM UTC+2, Matt Yule-Bennett wrote:

This would be cool. Would you like to raise a pull request to add it?

Yes. What i need to do? Or just wait your activity?

···

On Sunday, March 19, 2017 at 6:45:13 PM UTC+2, Matt Yule-Bennett wrote:

Fork the https://github.com/nameko/nameko repo, make your changes in a
branch, and then create a pull request from that branch back to the master
branch on nameko/nameko.

There's a decent guide here:
https://gist.github.com/Chaser324/ce0505fbed06b947d962

On Saturday, March 18, 2017 at 4:29:30 PM UTC, trex....@gmail.com wrote:

On Saturday, March 18, 2017 at 1:16:38 PM UTC+2, Matt Yule-Bennett wrote:

This would be cool. Would you like to raise a pull request to add it?

Yes. What i need to do? Or just wait your activity?

I make PR, but receive error from tests -
https://travis-ci.org/nameko/nameko/builds/212789948
I have no idea - whats wrong - who may help me?

···

On Sunday, March 19, 2017 at 6:45:13 PM UTC+2, Matt Yule-Bennett wrote:

Fork the https://github.com/nameko/nameko repo, make your changes in a
branch, and then create a pull request from that branch back to the master
branch on nameko/nameko.

There's a decent guide here:
https://gist.github.com/Chaser324/ce0505fbed06b947d962

On Saturday, March 18, 2017 at 4:29:30 PM UTC, trex....@gmail.com wrote:

On Saturday, March 18, 2017 at 1:16:38 PM UTC+2, Matt Yule-Bennett wrote:

This would be cool. Would you like to raise a pull request to add it?

Yes. What i need to do? Or just wait your activity?