storage grid includes several software logs to assist with troubleshooting the primary storage grid log is the audit log which is configurable and can include logging for system events client reads and writes ilm operations and more additionally storage grid load balancers have their own access logs that track requests made to and serve from each load balancer this log includes useful information about S3 requests to the endpoint including the HTTP Response Code the client IP and the response time with the 11.9 software release load balcer endpoint access logs can now be forwarded to an external syis log server increasing the observability of our load bouncers this 11.9 grid is configured to forward messages to an external elk server I've enabled forwarding of access logs which is new in 11.9 now whenever the load balancer on this grid receives any requests the logged information will be forwarded to our elk server now let's go ahead and send some S3 requests to the grid I went ahead and created a demo tenant and bucket on the grid and uploaded an image now I'm going to upload a few more images and I'm going to go ahead and download the zion. jpeg image which for already on the server I'm sending all of these requests to the load balancer endpoint on my grid now coming over to my elk server you can see my puts and gets have been logged and can be queried via kql you can see the individual puts for the first objects I uploaded and you can see the get for the zion. jpeg object I downloaded since the download was successful it returned to 200 status code and looks like we requested about 68 ,600 bytes in about 065 seconds for customers that take advantage of external syis log servers and have robust logging needs this new feature brings a new level of observability to storage GDs request handling thank you for watching