Apparently my last reply to this thread never made it through. Hope this one does! Mike, you're right that there are currently no btrfs metrics being emitted from garden-linux. There are currently no

Chris, I now know why this is happening. In ServeHTTP in reverseproxy in the httputil package[1] we make a copy of the incoming request for the outgoing request[2]. We then check[3] if the incoming

Simon, That is very interesting, nice investigation. I would have to do a little digging to try and see what exactly is going on, but the fact that the GoRouter is not setting the "X-Forwarded-For"

Disregarding F5/HAProxy comletely and going directly(10.230.18.134) to a Gorouter also yields different results depending on the client. $ curl -H "host:cf-env.domain.com" 10.230.18.134 $ wget

for 1., getting custom metrics from an app container (JMX, some business foo metric happened, etc) is a goal for the logging team, but it is lower than existing work to remove the collector. [image:

Hi, I am having exactly the same issue using develop branch and latest commit: $ git pull origin develop From https://github.com/cloudfoundry/cf-release * branch develop ->

this is a relevant tracker story to clean up after containers: https://www.pivotaltracker.com/n/projects/1158420/stories/96458012 -- Thank you, James Bayer

i removed the following nats: authorization_timeout: 10 use_gnatsd: true changed dea: &dea to dea_next: and removed dea_next: *dea and it seems to log App/0 again please note that because

Dieu, We use F5, just tried with the release HAProxy and I get concictent X-Forwarded-For between clients! Dont know how I managed to forget to check that. :) So in the HAProxy config the header

Hi, So am assuming that - to integrate tool like Introscope, if I go with firehose approach then would need to write a custom nozzle/forwarder? I have couple queries - 1. Can I add custom Metric

Thanks for the response Eric. It was very helpful. One last question. Any thoughts on what would be the best way to monitor free ephemeral disk space in my overcommitted situation? If

Thanks JT for your answer. Based on our experience, one of the best practice to share is that it's a good idea to set all the below four environment variables: http_proxy, HTTP_PROXY, https_proxy,

We have a workaround in place for the above issue (hack code to disable connection pooling) and it seems to have addressed this problem until we can get a better fix. We've also just filed a new bug

Thanks for the details. I deployed diego-docker-cache-release and I could run private docker images now. One note however. I had to modify the **property-overrides.yml *to add the IP:<port> of the

What do you use for your edge load balancer? You could try to set up your edge load balancer to strip x_forwarded_for sent in the request and set it again before forwarding on. In that way, I believe

In the Docker image case, the filesystem layer specific to the container is also deleted immediately when the container stops running (this is the same for buildpack based apps on Diego/Garden). Lower

Gist of diff: https://gist.github.com/simonjohansson/847e972f1459ea4cd65e Gist of debug output: https://gist.github.com/simonjohansson/3324b08fc42e5ac7105a Since it's quite hard to read in the

Hiya! Im looking into an issue where the x_forwarded_for have different values depending on what you are using to hit it with. With curl, w3m, lynx x_forwarded_for gets set to "sourceIP,

warden/DEAs keeps container file systems for a configured amount of time, something like 1 hr before removing the containers, i believe with standard removal tools. diego cells and garden removes

use the syslog nozzle to get system component logs and send them to your syslog server of choice. https://github.com/cloudfoundry-community/firehose-to-syslog wrote: -- Thank you, James Bayer