I’m wondering if there are any updates on this. thanks, Mike

The CF messages ingest OK into Splunk; None of the Diego messages ingest, not even the first line of their payload. The problematic deployment: · CF v212 · Stemcell 3012 (bosh-stemcell-3012-vsphere-es

We have a Diego 1099 deployment and syslog_daemon_config configured. We see a 1:1 mapping for Diego platform messages to syslog messages. In other words, for each syslog message that hits the wire, th

Thanks, Mike. I implemented and tested the second option and so far it appears to be working great. A side note: It’s a bit surprising CF allows names like api and uaa when the platform is using the s

It appears users can create their own routes named the same as critical endpoints such as api, doppler, loggregator, uaa, etc. In fact, I just created an app with routes doppler and loggregator and th

We had the same problem due to missing templates in our manifest. We initially used the example manifest snippet shown at https://github.com/cloudfoundry/loggregator which mentions only the doppler te