The http_server_request event reprsents an incoming HTTP request to your application. This is different from the HTTP Client Request Event in that it is an incoming request that your appication serves.

Started POST /applications

Example JSON Structure

{
  "event": {
    "server_side_app": {
      "http_server_request": {
        "headers": {
          "content-type": "application/json",
          "x-request-id": "2c3a0b24069af49b3de35b8e8c26765c1dba9ff0"
        },
        "host": "api.timber.io",
        "method": "POST",
        "path": "/applications",
        "port": 443,
        "query_string": null,
        "request_id": "2c3a0b24069af49b3de35b8e8c26765c1dba9ff0",
        "scheme": "https"
      }
    }
  }
}

Field descriptions

Name Type Description
headers map A map of raw header names and values. optional
host string The host of the destination URL. required, max-length: 255
method string The method of the request normalized to uppercase, ex: GET, POST, etc. required
path string The path of the destination URL. required, max-length: 5000
port number The port of the destination URL. optional
query_string string The query string of the destination URL. optional, max-length: 5000
request_id string The unique ID for this outgoing request, useful for request tracing. optional, max-length: 255
scheme string The scheme of the destination URL, ex: http or https. required

Using this data

Example queries:

  • Full path: event.server_side_app.http_server_request.host:api.timber.io
  • Short path: http_server_request.host:api.timber.io - Short paths are aliases allowing for simpler access to these fields.
  • Only this event: is:http_server_request

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