github.com/iron-io/functions@v0.0.0-20180820112432-d59d7d1c40b2/docs/operating/logging.md (about)

     1  # Logging
     2  
     3  There are a few things to note about what IronFunctions logs.
     4  
     5  ## Logspout
     6  
     7  We recommend using [logspout](https://github.com/gliderlabs/logspout) to forward your logs to a log aggregator of your choice.
     8  
     9  ## Format
    10  
    11  All logs are emitted in [logfmt](https://godoc.org/github.com/kr/logfmt) format for easy parsing.
    12  
    13  ## Call ID
    14  
    15  Every function call/request is assigned a `call_id`. If you search your logs, you can track all the activity
    16  for each function call and find errors on a call by call basis. For example, these are the log lines for an aynschronous
    17  function call:
    18  
    19  ![async logs](/docs/assets/async-log-full.png)
    20  
    21  Note the easily searchable `call_id=x` format.
    22  
    23  ```sh
    24  call_id=477949e2-922c-5da9-8633-0b2887b79f6e
    25  ```
    26  
    27  ## Metrics
    28  
    29  Metrics are emitted via the logs.
    30  
    31  See [Metrics](metrics.md) doc for more information.
    32