2020-09-21 19:46:22 UTC - Brendan Doyle: <https://github.com/apache/openwhisk/pull/4981>
Still unclear to me if we need these logs. I'd like to know what the need is for container concurrency, but changing at least to warn now should be good enough for us. @Tyson Norris https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1600717582009500?thread_ts=1600390173.002200&cid=C3TPCAQG1 ---- 2020-09-21 20:02:16 UTC - Tyson Norris: It is helpful to know the error when customers ask why their activation failed, even though they can look it up in the activations; we also can look it up in the activations, but it is just convenient to have it in the logs as well https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1600718536009900?thread_ts=1600390173.002200&cid=C3TPCAQG1 ---- 2020-09-21 20:17:16 UTC - Brendan Doyle: it seems like we're mixing client logs with invoker server logs and will just result in spam at scale when we don't have control over all of our clients and what they're doing. I still don't think these logs really belong above debug especially if they're just available through the activation. If there was a difference in retrievability for concurrency, it would make more sense to me. I'm fine with getting it in as warn, but that's my two cents https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1600719436010100?thread_ts=1600390173.002200&cid=C3TPCAQG1 ---- 2020-09-21 23:44:27 UTC - Tyson Norris: I understand how it can be problematic; another option is to add a config flag to require opt-in for including these logs. If you want to implement this, it would be fine to default it to off (no logs), and we will explicitly enable it on our system. https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1600731867000200?thread_ts=1600390173.002200&cid=C3TPCAQG1 ---- 2020-09-21 23:45:50 UTC - Brendan Doyle: yea I think that's a good idea https://openwhisk-team.slack.com/archives/C3TPCAQG1/p1600731950000400?thread_ts=1600390173.002200&cid=C3TPCAQG1 ----
