Over a million developers have joined DZone.

Cloud Foundry Logging Sources Deciphered

DZone 's Guide to

Cloud Foundry Logging Sources Deciphered

A developer shows us how to decipher the seemingly cryptic error messages you can get when your cloud platform isn't performing as it should.

· Performance Zone ·
Free Resource

Ever deployed a cloud foundry app and ran into errors? I did and still do. My typical reaction is to request the recent app logs and to analyze them for the root cause. The logs contain those strange (if you don't know them) codes, e.g., RTR, STG, APP, PROC, WEB or more. Here is how to decipher them and use them to your advantage.Happy Apps in the Cloud

The codes above denote the Cloud Foundry component emitting the log entry. You can find a list of those component identifiers in the Cloud Foundry documentation or in the IBM Cloud (Bluemix) documentation on Log Sources. There are many component names. I found that remembering the following helps a lot:

  • RTR: This is the router which channels HTTP requests to an app. Here you find information about the request itself including client information.
  • STG: The staging phase has details about the deployment and restaging of an app. They help with initial errors.
  • APP: If your app writes information to stderr or stdout, then you will find it here. For some apps, this could be the well-known "printf debugging."

The log entries have either an OUT if the information is from stdout or ERR if from stderr. Otherwise, there is not much to remember. Happy debugging! If you have feedback, suggestions, or questions about this post, please reach out to me on Twitter (@data_henrik) or LinkedIn.

cloudfoundry ,debugging ,logs ,performance ,cloud performance

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}