Hi Vadim, This looks helpful to get better insight in runtime operational stats!
> It has some advantages over to the prior approach (sending them to CouchDB). Can you share some details on how this is currently being done with CouchDB. Do we have any analytics view configured which computes these numbers currently? > Now it would be possible to simply connect a custom micro service to Kafka and consume the activations in real-time. May be we also include a basic default implementation out of the box which collect aggregated stats using Kamon metrics already being used Chetan Mehrotra On Mon, Apr 16, 2018 at 9:51 PM, Vadim Raskin <raskinva...@gmail.com> wrote: > Hi everyone, > > > I’ve just opened a PR that enables sending activation metadata to Kafka. > It has some advantages over to the prior approach (sending them to > CouchDB). Now it would be possible to simply connect a custom micro service > to Kafka and consume the activations in real-time. Some of the use cases it > might cover: activation metrics - collect the data and push them into a > custom time-series database; user activity audit; activation analytics - > potentially get some insights with KSQL. > > > At the moment I’ve created a new kafka topic called events, which will > include messages from Controllers and Invokers. It encompasses the > following data collected from a single activation: > > > concurrentActivations > throttledActivations > statusCode > initTime > waitTime > duration > kind > > > Probably some more metadata will affiliate this list soon. > > > Just wanted to give a short heads up here. The PR I mentioned: > https://github.com/apache/incubator-openwhisk/pull/3552 > > > Thank you, > > > Vadim.