Nick Mitchell wrote on 10/04/2018 12:06:14 PM:
>
> from a usability perspective, there is something quite attractive about
> having ready access to logs (and activation records generally)... while
> developing. i think most of the woes we encounter with logs come from
high
> volume actions (eith
"James W Dubee" wrote on 10/04/2018 11:45:34 AM:
> From: "James W Dubee"
> To: dev@openwhisk.apache.org
> Date: 10/04/2018 11:49 AM
> Subject: Re: Logstore usage during `activation get`
>
> On a similar note, I don't think we should be storing activation
> responses at all.
>
+1 Responses can c
from a usability perspective, there is something quite attractive about
having ready access to logs (and activation records generally)... while
developing. i think most of the woes we encounter with logs come from high
volume actions (either exercised in prod, or during a high volume test)?
i real
Hey guys,
For scalability concerns, I think it is preferable to separate logs from
activation records entirely. Doing so would require users to use the logs
API, or whatever tools are provided by the underly logging service. We
should focus on serverless technology and delegate log handling to se