Figure out which logs make sense for customers and create API Gateway dashboard for Kibana, initial ideas:

ip_address: Geographical map chart to visualize the distribution of requests from different regions based on the requester's IP address.

request_id: This field represents a unique identifier for each request. It is not typically suitable for visualization and is more useful for tracking or correlation purposes.

http_method: Bar chart to visualize the frequency of different HTTP methods used in the requests.

protocol: Since API Gateway APIs can accept HTTP/2 requests but send requests to backend integrations using HTTP/1.1, this field may not require visualization as it is generally constant.

request_time: Line chart or time series chart to effectively show the request trends over time.

response_length: Line chart or histogram to show the distribution or changes in response payload length (in bytes) over time.

route_key: Table or donut chart to display the distribution of requests among different selected route keys.

status: Pie chart or bar chart to visualize the distribution of different response status codes.

caller: Table or any suitable chart to show the principal identifier of the caller making the request.

user: Table or any suitable chart to show the principal identifier of the user making the request.

resource_path: Table or any suitable chart to show the path to your resource.

connection_id: Table or any suitable chart to show a unique ID for the connection that can be used to make a callback to the client.

event_type: Bar chart or pie chart to visualize the distribution of different event types (CONNECT, MESSAGE, DISCONNECT).