I am getting closer to putting my Elixir backend API in production and have a question about logging. Currently when a 500 error occurs in an API call, the entire Plug is posted to my logging service. This includes the JWT used in the request and secret key base used to decrypt the JWT. Is there an…

config :phoenix, :filter_parameters, ["password", "secret"] Phoenix.Logger — Phoenix v1.8.8 or check your logging service for equivalent..

Gotcha, but that’s just for incoming parameters correct? There’s no way to filter sensitive information logged during an error?

I have the same situation right now. I am making a request to a remote system and if it fails, I log the entire HTTPoison response, which might contain login credentials. Currently: Body: {:form, [{"email", "user@example.com"}, {"password", "secret1234"}]} But maybe in the future, if the remote AP…

can you post full (pseudo) code and error (sensitive data deleted..) I imagine one has to filter manually - but maybe it’s possible to create/have a “deep” nested filter that goes through things.. eg config :phoenix, :deep_filter_logs, [“password”, “secret”]

Basically, what I do is this: defimpl AppGateway.Error, for: AppGateway.Errors.RemoteServiceError do def status(_), do: AppGateway.Errors.RemoteServiceError.status() def log_message(error) do """ Error while calling Remote Service! Method: #{error.method} Url: #{error.url} …

look at nested_filter nested_filter | Hex or deep_clean deep_clean | Hex else a regex on the string containing sensitive data?

I think filtering the actual data is much easier and less error prone than an unstructured string dump of the data…

Seems like the nested_filter lib only works with maps but I am dealing with quite a few structs. Also, if the request body contains a JSON string, it won’t help at all.

Filter sensitive logging data

Questions & Help Questions

outlog August 6, 2017, 3:22pm 2

config :phoenix, :filter_parameters, ["password", "secret"]

or check your logging service for equivalent..