---
title: "goaccess access.log analysis on a Non-Production environment"
date: "2025-02-05T23:48:57+00:00"
summary:
image:
type: "article"
url: "/acquia-cloud-platform/help/94091-goaccess-accesslog-analysis-non-production-environment"
id: "ef2c2af7-fa34-475b-84bd-38c46dc16a80"
---

In this article we will be going over a quick example on how to use [goaccess](https://goaccess.io/) to analyze the Apache [access.log](/node/56388) in a non-production Acquia Cloud Platform environment.  
**Make sure to replace content in** `[]` **with your specific use case**

For non-production environments which rely on a single instance to serve traffic analyzing the logs with goaccess is relatively simple.

First you SSH to the appropriate environment `example.env` and navigate to the `access.log` [location](/node/56379). 

In order to analyze the logs you need to pa them to `goaccess` together with the appropriate log format. For example:

    example@staging-123:/var/log/sites/[example].[env]/logs/staging-123$ cat access.log | goaccess --log-format=COMBINED -o ~/report.html

... or if you would like to check historical gziped logs:

    example@staging-123:/var/log/sites/[example].[env]/logs/staging-123$ zcat access.log | goaccess --log-format=COMBINED -o ~/report.html

The report is now available for you to download using the same methods described [here](/node/56379) but with the location being `/home/[example]/report.html` instead.

Note that you can actually place the `report.html` to a location which is served by your sites like `/var/www/html/example.env/docroot/sites/default/files` by modifying the above command and then view the result from your browser. **Be careful you may want to add http authentication to that as it will be publicly available!**