The http_client_response event represnts the response of an outgoing HTTP request from within your application. This is different from the HTTP Server Response Event in that it is a response to an outgoing request.

Outgoing HTTP response from timber 200 in 52.2ms

Example JSON Structure

{
  "event": {
    "server_side_app": {
      "http_client_response": {
        "body": "{\"key\": \"value\"}",
        "headers": {
          "content-type": "application/json",
          "x-request-id": "2c3a0b24069af49b3de35b8e8c26765c1dba9ff0"
        },
        "status": 200,
        "request_id": "2c3a0b24069af49b3de35b8e8c26765c1dba9ff0",
        "service_name": "timber",
        "time_ms": 52.2
      }
    }
  }
}

Field descriptions

Name Type Description
body string The body of the response. This is disabled by default and can be enabled by configuring our libraries appropriately. optional, max-length: 5000
headers map A map of raw header names and values. optional
status number The status code of the response. required
request_id string The unique ID for this outgoing request, useful for request tracing. optional, max-length: 255
service_name string An optional label for the service being communicated with, ex: stripe, timber, etc. optional, max-length: 255
time_ms number The time taken to receive a response in milliseconds. required

Using this data

Example queries:

  • Full path: event.server_side_app.http_client_response.status:200
  • Short path: http_client_response.status:200 - Short paths are aliases allowing for simpler access to these fields.
  • Only this event: is:http_client_response

See our doc on using context & event data.

Questions? Need help?

Chat with us, just click the talk button in the bottom right of this page.

Chat with us

Start a trial - 15 days free

Log better and solve problems faster, today. Less than 1 minutes to install.

Start a trial