pi-tools

• debug-tools: Tools for obtaining logs and application information from production or staging enviornments.
• helpful-tools: Just a set of bash tools that have been collected over time. These tools are not actively maintained.
• newrelic-tools: Some scripts used to manage New Relic. Their APIs are undocumented and lack traditional API security like API keys.
• release-tools-archive: Old scripts written to mange aspects of the release. These tools are no longer used.

Debug Tools

• cfLoginDallas.sh - Logs you into the PI org & space for Dallas Production
• cfLoginLondon.sh - Logs you into the PI org & space for London Production
• getAppsInfo.sh - Grabs all ACTIVE apps and runs cf app, cf logs --recent, and cf events and outputs to the following log files
  • appStatus_*.log - Result of cf app <APP>. Contains CPU & Memory information.
  • appLogs_*.log - Result of cf logs <APP> --recent. Contains recent log statements but for only a limited time slice.
  • appEvents_*.log - Result of cf events <APP>. Contains events, including crashes, restarts, etc. for the app..
• appStatusByCPU.sh - Must be ran after getAppsInfo.sh. Aggregates and filters all the appStatus_*.log files to show applications by CPU usage, with highest usage at the bottom.
• appStatusByMemory.sh - Same as appStatusByCPU.sh but sorts by memory usage, again with highest usage at the bottom. Important when looking at memory ensure you're comparing the memory used to the memory limit.
• start-all-logs.sh [filter] - Streams logs from all ACTIVE apps, filtered by [filter] (if provided), to files of the format <APPNAME>_log. e.g., running ./start-all-logs.sh conn Will only grab connector logs. Note This script runs cf logs in background processes. You can see these processes by running ps xa | grep 'cf logs'
• tail-all-logs.sh - Must be ran after start-all-logs.sh. Essentially runs tail -f pi_*.log to stream all logs to stdout.
• stop-all-logs.sh - Run when you're done capturing logs.