Thanks for the input, that's a good call. A colleague of mine (who is currently on vacation) did look at that... Sadly he's not around to ask what he tested. -- Regards, Daniel

Hi Owais, I'm not sure if it helps or not, but I can tell you that gnatsd has some monitoring api endpoints to get information. https://github.com/nats-io/gnatsd#monitoring Owais Mohamed

" There is no way to to pull logs and metrics of entire CF instance into such agent based monitoring tools, it has to be binded everytime for each app ?" Fork the java-buildpack add your agent and

Thanks Juan, I will try to setup a poller for this to achieve similar functionality. Do you know if there is already proposal for the better notifications - if yes, could you point me to it? I Would

Hi, What version of the cf cli are you using? There was an update for logging in cf v208 that changed the endpoint. Thanks, Joseph & Dan, OSS Release Integration Team

Hi Juan, Is this question a duplicate of the other one? Thanks, Amit bren(a)juanantonio.info> wrote:

You may need to configure the application-level security groups to allow apps running in containers to talk to system components such as the Cloud Controllers. You will likely only want to allow this

The directory is on your computer. You probably got it by cloning the repository from github, so only you know where you cloned it. If you are using a unix machine, you can use the "find" utility to

Thanks for your reply Daniel. So you are saying that - for any agent based monitoring tools like - NewRelic, AppDynamics, Wily-Introscope, Dyna-trace etc. firehose approach doesn't make any sense,

Thank you for your patience as we continue to pilot Mailman 3 with the Cloud Foundry project. We do appreciate any feedback (and bug reports!) you have from using the system, which can be sent to

Hi, Mike, Apologies, I emailed this to cf-dev a few days ago, but it seems not to have gone through. Anyway, thanks for asking about the different configuration values Diego exposes for disk and

Hi, Maggie, Apologies, I sent this reply to cf-dev earlier, but it seems not to have gone through. Anyway, the 'cf.internal' domain is used internally by CF and Diego components to do service

You should not change anything in your DNS servers. It is purely internal; jobs that need to reach other services over the internal domain should be colocated with consul_agents which will serve

Then how should I config my DNS server? Which host/job’s IP should be mapped to domain “service.cf.internal”? I also attached the etcd job log. Would you please help to take a

Hello, you can add the timeout in your manifest itself. https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#timeout Thanks Ronak -- View this message in context:

Hi guys, How can I increase the request timeout in CF? I would like to give more time to my app to send a response to the requests before getting a timeout. Should I increase it in the buildpack? If

Hi guys, How can I increase the request timeout in CF? I would like to give more time to my app to send a response to the requests before getting a timeout. Should I increase it in the buildpack? If

Hi guys, How can I increase the request timeout in CF? I would like to give more time to my app to send a response to the requests before getting a timeout. Should I increase it in the buildpack? If

- cf logs APPNAME --recent does not show any difference - i created my deployment manually because spiff templates do not work with openstack without neutron so i i update my deployment manifest with

that commit you link to is pretty old (well over a year) and is not the problem between v207 and v214. there is likely some configuration issue. i sent you a response on the other thread you opened