- 
                Notifications
    You must be signed in to change notification settings 
- Fork 418
Logs tail command
        Kenneth Auchenberg edited this page Oct 31, 2019 
        ·
        1 revision
      
    logs tail establishes a direct connection with Stripe and enables you to tail your test mode Stripe API request logs in real-time from your terminal.
By default, logs tail will display all of your test mode request logs. To begin log tailing, run:
$ stripe logs tailA number of built-in filtering options are also supported:
- 
--filter-account, (Connect only) supportsconnect_in(incoming Connect requests),connect_out(outgoing Connect requests), andself(non-Connect requests)
- 
--filter-ip-address, supports a direct match with any ip address
- 
--filter-http-method, supportsGET,POST, andDELETE
- 
--filter-request-path, supports a direct match to any Stripe path (e.g.,/v1/charges)
- 
--filter-request-status, supportssucceededandfailed
- 
--filter-source, supportsapianddashboard
- 
--filter-status-code, supports any status code that is a200,400, or500(e.g.,404)
- 
--filter-status-code-type, supports2XX,4XX, and5XX
Multiple filters can be used together, where a log must match all filters to be shown:
$ stripe logs tail --filter-http-method POST --filter-status-code-type 4XXMultiple values for a single filter can also be specified as a comma-separated list, where a log only needs to match one of the values:
$ stripe logs tail --filter-http-method GET,POST