The GRAX application always outputs structured logs in JSON format to
stdout and optionally streams those same structured logs to hq.grax.com for monitoring. On specific infrastructures (pre-built), GRAX also pushes logs to Cloudwatch (or platform equivalent). Here, we'll explain what the contents of those logs looks like, and what customers can do with them.
NOTE: Log access for grax-managed applications and infrastructure is not available. In these environments, GRAX Engineering handles all monitoring and troubleshooting.
GRAX logs are focused around GRAX's ability to monitor and troubleshoot the application; as such, they include:
- worker/queue status information
- job status information
- cpu, heap, and memory profiles
- function timing information
- network calls (only path, method, and returned status)
- error stack traces (where and what in the GRAX code hit an error)
GRAX logs are purpose built to never log or expose customer information or application secrets; as such they never include:
- user credentials
- configuration secrets
- web session secrets (cookies, etc)
- Salesforce record data
As stated above, logs from GRAX are intended for consumption by GRAX engineers. We do not publish documentation nor provide training on understanding the internals of the GRAX application or its behavior. This means that logs will not provide value to teams monitoring GRAX directly without the assistance of GRAX support.
If you have a compliance requirement related to log capture (like the use of Splunk), connectors exist for Cloudwatch. If such requirements require agents to exist on the instance itself, the app must run with the self-managed, customer-built infrastructure model.
GRAX logging does not extend to infrastructure components. In situations where customers control and manage the infrastructure running GRAX, monitoring and alerting can be configured independently. For more information on monitoring GRAX infrastructure, please review our monitoring documentation.
Updated 22 days ago