I have often seen the case where teams developing applications that depend on many service instances use a single space for dev/test so they don't have to recreate all the SIs in multiple spaces. Each

By the `application_uris` data are broken logic, VCAP_SERVICES is also broken and should be removed as it doesn't reflect service binding changes. In my (strong) opinion it doesn't make any sense to r

So, I certainly like the idea of namespacing Diego specific properties. The job level granularity is excessive though. cf-release is also very old so a lot of its properties could be rethought/reorgan

I have created and used quite a few BOSH releases and the property namespacing feels very odd to me. I'm very curious to understand the reasoning behind it. I can't reproduce my 2048-bit key problem.

I just got Diego successfully integrated and deployed in my Cloud Foundry dev environment. Here's a bit of feedback. One of the really nice features of BOSH is that you can set a property once and any

Shannon, The polling API in the the Asynchronous Operations documentation suffers from the same problem. Perhaps the .../last_operation request could include a service_id query parameter? Thanks, -Mik

I think our situation is a little bit different since we have a custom syslog server that send logs directly to our Splunk indexers rather than going through a Splunk forwarder that can aggregate mult

That's fair. I think Mike Youngstrom is right. All of our logging problems would go away if our applications could talk syslog to Loggregator. Capturing stdout and stderr is certainly convenient, but

Actually, this might explain why some of our customers are so frustrated trying to read their stack traces in Splunk. :\ So each line of a stack trace could go to a different Doppler. That means each

One of the really nice features of the V2 Service Broker API is the ability to broker multiple services from a single process. Each service provides its unique id in the broker catalog. The Cloud Cont

Metron's documentation [1] says "All Metron traffic is randomly distributed across available Dopplers." How random is this? Based on observation, it appears that logs for an individual application ins