You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by gi...@git.apache.org on 2017/09/29 19:04:03 UTC

[GitHub] vvraskin commented on issue #2695: Logstore SPI

vvraskin commented on issue #2695: Logstore SPI
URL: https://github.com/apache/incubator-openwhisk/pull/2695#issuecomment-333211687
 
 
   A follow up after the short discussion we had during the community interlock. 
   
   In case we need to support both UI and CLI based logs, I think it would be advantageous to stream the logs out to some internal bus/buffer (e.g. Reddis, Elasticsearch) and keep it there for a short period of time, say 10 mins. 
   Then it would be possible either to keep the previous api or create a separate component just for log streaming (a concept similar to CF loggregator), so the CLI and other log consumers could connect to it and redirect them to whatever backend is needed.
   
   That would provide more flexibility for the end users, say everyone is able to select a particular logging backend within one OpenWhisk provider versus an OW operator defining one backend for the whole deployment. However I?m not sure if an SPI concept allows to specify several implementations to run in parallel. 
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services