When log parameter in the Service Management API is not correct (e.g. does not contain the "code" attribute), backend is responding with a 500 error: we probably should be just ignoring invalid values instead.

(alternatively, we could just respond with a 400 to give the user some hint that they are sending invalid data, but probably the "log[code]" is unimportant compared to just reporting the usage, so maybe it's actually not desired to fail the whole request because of log value)