Thanks for quick response, Michael.

But I am using DEA CF 235 only. Is this supported on non-Diego version of
CF ?

Regards,
Vinod

On Fri, Sep 16, 2016 at 2:25 PM, Michal Kuratczyk <mkuratczyk(a)pivotal.io>
wrote:

Hi Vinod,

You can't do this using this approach indeed but Cloud Foundry provides
the Firehose component with all logs from all applications as a stream you
can use to feed you ELK stack.
The easiest way will be to deploy firehose-to-syslog nozzle (
https://github.com/cloudfoundry-community/firehose-to-syslog) which will
capture that data and send it to your ELK's syslog endpoint.

You can read more about Firehose here https://docs.
cloudfoundry.org/loggregator/architecture.html#firehose

Best regards,

On Fri, Sep 16, 2016 at 8:17 PM, Vinod Singh <vinoddandy(a)gmail.com> wrote:

Hi All,

We are redirecting the application logs to ELK system from Cloud Foundry
deployment.

The issue is : we have to create a user provided service instance in each
space of each user's org to provide logging url to the application. This is
tedious because each time I create a new space I have to create a CUPS for
logging.

Solution : is it possible to create the service instance by CF admin in
his space/org and share across all user's orgs ? I know it is not possible
today because service instances are restricted to user's space only.

Can CF provide some solution in future to fulfill above user case ?

Thoughts/Comments ?

Regards,
Vinod

--
Michal Kuratczyk | Solution Architect | Pivotal Inc.
Mobile +48602421588 | mkuratczyk(a)pivotal.io