Adding filter clauses
Use simple SQL-like syntax to filter your requests.
Basic filtering
You can filter your app’s requests based on properties like request path, request method, response status code, and many
more. These filters are expressed using the syntax of SQL WHERE clauses. Here’s an example of filtering requests that
have a 5XX status code by using the filter http_resp_status_code LIKE '5%':
See here for the list of properties you can filter on with Subtrace out of the box.
Autocompletion
Notice that in the video above, we didn’t type out the entire name http_resp_status_code. We were able to type just a
section of it, and use the ⇥ Tab key to autocomplete the name. This works similarly to shells like bash or zsh.
When we detect that an autocomplete suggestion is available, it will be displayed next to the current word being typed.
If there are multiple available suggestions, you can choose among them using the ↑ and ↓ arrow keys.
Recognized properties
These are the properties that Subtrace recognizes for filters. But that doesn’t mean these are the only properties you can filter on. You can add some additional information to your request/response headers to allow you to filter on custom properties.
Basic information
hostnamehttp_durationprotocolservice
Request properties
http_client_addrhttp_is_outgoinghttp_req_body_size_bytes_wirehttp_req_content_encodinghttp_req_content_lengthhttp_req_content_typehttp_req_hosthttp_req_methodhttp_req_pathhttp_req_transfer_encodinghttp_req_x_forwarded_forhttp_server_addrhttp_versiontls_server_name
Response properties
http_resp_body_size_bytes_wirehttp_resp_content_encodinghttp_resp_content_lengthhttp_resp_content_typehttp_resp_status_codehttp_resp_transfer_encoding
Process information
process_command_lineprocess_executable_nameprocess_executable_sizeprocess_idprocess_user
Google Cloud specific information (if running on GCP)
gcp_project
Kubernetes specific information (if running on Kubernetes)
gke_cluster_locationgke_cluster_namegke_node_namekubernetes_namespace