[CLOSED] Establish logging policy in cases of error and propagation of actual exceptions about akka-http HOT 4 CLOSED

Comment by rkuhn
Wednesday Sep 17, 2014 at 09:11 GMT

We need to give the user full control over the logging: the library shall not log by itself but allow everything to be logged at the user level. The principal approach here is to publish flows of log events, one for the binding and one for each connection. A log event contains:

• timestamp
• source identifier (bound address and/or peer address)
• structured message (case classes for different occurrences)

We will need to write adapters to SLF4J and the usual suspects in order to identify whether structured messages need to derive from some common parent type.

from akka-http.

Comment by sirthias
Friday Oct 03, 2014 at 11:49 GMT

/cc @sirthias

from akka-http.

Comment by jrudolph
Wednesday Feb 11, 2015 at 16:06 GMT

Also, see the suggestions in #16842, spray/spray#243 and https://groups.google.com/forum/?fromgroups#!forum/spray-user:

• ERROR for unexpected internal conditions
• WARN for remote peer triggered errors

from akka-http.

Comment by ktoso
Thursday Sep 08, 2016 at 14:53 GMT

Ticket moved to github.com/akka/akka-http
Rationale for the move discussed here: akka/akka-meta#27
If you are interested in contributing or tracking this issue, please comment in akka-http instead from now on :-)

from akka-http.