Pivotal Knowledge Base

Follow

OSS Tool to Identify Noisy Applications in Pivotal Cloud Foundry 1.11 and above

Environment

Pivotal Cloud Foundry (PCF) 1.11 and later versions

Purpose

Logging format enhancements were introduced in PCF 1.10 and 1.11. The move from UDP to gRPC as a transport protocol for the firehose was done in PCF 1.10. In PCF 1.11, Scalable Syslog was introduced which modified the formatting of application logs as they appeared in the firehose.

Expected results:

  • Message drop frequency is expected to be reduced overall within PCF.
  • Scalable Syslog makes minor changes to how logs are formatted in the firehose.

Example 

PCF Version 1.10 and prior

{"timestamp":1485876600.920807362,"process_id":4145,"source":"doppler",
"log_level":"warn","message":"TB: Output channel too full","data"
:{"appId":"xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxx","destination":"syslog:
//<SYSLOG-ENDPOINT>:PORT","dropped":99,"total_dropped":14158},"file":
"/var/vcap/data/compile/doppler/loggregator/src/truncatingbuffer/truncating_buffer.go",
"line":112,"method":"truncatingbuffer.(*TruncatingBuffer).forwardMessage"}

PCF Version 1.11 or later

2018/01/16 09:49:57 Dropped (egress) 1000 envelopes

Procedure

To identify noisy apps in PCF Version 1.11 or later, please refer to the Open Source project outlined in https://github.com/cloudfoundry/noisy-neighbor-nozzle

For PCF Version 1.10 and prior, appId is included in the logs as stated above. 

Comments

Powered by Zendesk