F2S_DISABLE_LOGGING = true -- v5.0.0 -- does not disable logging about firehose-to-syslog HOT 8 CLOSED

The documentation says to create a UAA client with:
--authorities doppler.firehose,cloud_controller.global_auditor

But apparently "cloud_controller.global_auditor" doesn't have sufficient authority to read the application environment vars so the IgnoredApp property in the BoltDB is never changed to true.

Changing your UAA Client to have "cloud_controller.admin_read_only" allows the app to be ignored again.

from firehose-to-syslog.

Should work, the issue maybe could be the time of the apps info are reloaded in boltDB or memory.

from firehose-to-syslog.

The env var was set over weekend, and it was still not recognizing it Monday. Did something change in the 5.0.0 release to how the environment data is gathered from CF?

from firehose-to-syslog.

Ok when digging through the caching code...

It looks to never goes back to CF and recache it up again due to rv.TTL.After

If we were to change the rv.TTL.Before then it would re-lookup it when the TTL has expired...

var rv entity
err = c.store.Get(makeCacheStorageKey(entityType, uuid), &rv)
switch err {
case nil:
	if rv.TTL.Before(time.Now()) {
		return &rv, nil
                     //continue
	}
	// else continue
case ErrKeyNotFound:
	// continue
default:
	return nil, err
}

from firehose-to-syslog.

It should go back, but randomly as cache will be invalidated https://github.com/cloudfoundry-community/firehose-to-syslog/blob/develop/caching/caching_lazyfill.go#L153

from firehose-to-syslog.

Is there a way to test that, because that is not what we are seeing? As we pulled the boltdb from the VM and looked at it

from firehose-to-syslog.

We will give it a try and see it fixes the issue

from firehose-to-syslog.

The above fixes the problem -- we recreated the UUA client with the correct permission and I used that setting today to stop an apps logging. -- I did have to cause a cf restage [app_name] to pick up the environmental setting

from firehose-to-syslog.