Viewing Logs for your Flightcontrol Project
Your Flightcontrol projects run on Amazon Web Services (AWS) and use AWS CloudWatch for runtime logging.
We provide web-based log viewers for the Build Logs and Deploy Logs in the Flightcontrol Dashboard, and you can also view logs in the AWS Console or using the AWS CLI.
In this guide, we'll explain the differences between the three different log types that Flightcontrol deploys create, and then explain how to view each different type of log.
Flightcontrol deployments have three different types of logs:
When you use the Nixpacks build type or the Custom Dockerfile build type, Flightcontrol kicks off a build process to turn your source code repository into a Docker image.
With the Nixpacks build type, you will find the plan for the Nixpacks build as part of the build logs output. A sample from a Flask build with Nixpacks is shown below:
... 10:57:40 AM: 10:57:40 AM: ╔═══════════════════════════════ Nixpacks v1.6.0 ══════════════════════════════╗ 10:57:40 AM: ║ setup │ python38, gcc ║ 10:57:40 AM: ║──────────────────────────────────────────────────────────────────────────────║ 10:57:40 AM: ║ install │ python -m venv /opt/venv && . /opt/venv/bin/activate && pip ║ 10:57:40 AM: ║ │ install -r requirements.txt ║ 10:57:40 AM: ║──────────────────────────────────────────────────────────────────────────────║ 10:57:40 AM: ║ start │ gunicorn --bind 0.0.0.0:3000 wsgi:app ║ 10:57:40 AM: ╚══════════════════════════════════════════════════════════════════════════════╝ 10:57:40 AM: ...
Both the Nixpacks and the Dockerfile builds will also show the output for the Docker image creation. You can use this to examine exactly what is being included.
If desired, you can also click the "View Logs with AWS" button to view the build logs in the AWS Console. Flightcontrol uses AWS CodeBuild to perform the build.
The build logs should always be available for any deployment, whether there is a success or a problem.
Deploy logs appear after a build is successfully created, during the initial deploy process. The deploy logs will remain available if the deployment fails, and the application is unable to successfully start serving traffic. If the deployment is successful, the same information will be available in the runtime logs.
These deploy logs are very useful as a debugging tool for failed deployments, because you can find out exactly what went wrong.
AWS CloudWatch stores the deploy logs. These are the standard output written out by your application's start process.
To find the deploy logs, check your environment in the Flightcontrol dashboard. If you have a successful build and either a running deployment or a failed deployment, you will see the "Deploy Logs" button, similar to the following screen:
After clicking the "Deploy Logs" button, the "Deploy Logs" window will open for you to inspect the logs, such as to the following screen:
If your deployment was successful, and your application started serving traffic, you will not see the "Deploy Logs" button. You will see a button for the next type of logs, the runtime logs.
Runtime logs show the output from your application's services, running on the ECS Fargate cluster. These logs are stored in AWS CloudWatch, and you can either use the AWS console or the AWS command line interface to view the logs.
You will see runtime logs for web applications and workers with successful deployments.
The Flightcontrol Dashboard has a direct link to the runtime logs in the AWS Console for each service.
Click the "Runtime Logs" button next to a successful deploy, and you will be taken to the AWS Console to view the logs. The CloudWatch screen will show the list of log streams - the most recent deployment will be at the top.
Choose one of the log streams to view the log events (typically, the latest stream is at the top). Each line printed to standard out by the application will be shown as a separate log event with a timestamp.
You can use the standard CloudWatch functionality to filter log events by specific text or a date range. If you desire, you can also view the logs as plain text as well, to get more horizontal space for each row.
Each Fargate instance of your application will send information into your runtime logs, so these can be noisy. In addition, ECS Fargate sends a health check request to your servers (every 60 seconds, by default), so you will likely see a log event for each of these health checks.
If you would like to see your runtime logs in a tail environment, you can use the AWS Command Line Interface (version 2) to view the logs.
You will need to install the command line interface (the
aws command) and configure it with your AWS credentials. You can find more information about this in the AWS CLI documentation (opens in a new tab).
Once you have the AWS CLI installed and configured, you can use the following command to tail the logs for a specific service:
aws logs tail <group-name> --region <region> --follow
An example of this would be:
aws logs tail /ecs/flask-server-1tx0kknTaskDefinition --region us-east-2 --follow
With the output of:
2023-05-31T21:28:30.247000+00:00 clic7vn8n0odur72bdbpoqvtl/flask-server-1tx0kkn/9796db1e2ac24761b456e686761a55ac [2023-05-31 21:28:30 +0000]  [INFO] Starting gunicorn 20.1.0 2023-05-31T21:28:30.248000+00:00 clic7vn8n0odur72bdbpoqvtl/flask-server-1tx0kkn/9796db1e2ac24761b456e686761a55ac [2023-05-31 21:28:30 +0000]  [INFO] Listening at: http://0.0.0.0:3000 (1) 2023-05-31T21:28:30.248000+00:00 clic7vn8n0odur72bdbpoqvtl/flask-server-1tx0kkn/9796db1e2ac24761b456e686761a55ac [2023-05-31 21:28:30 +0000]  [INFO] Using worker: sync 2023-05-31T21:28:30.252000+00:00 clic7vn8n0odur72bdbpoqvtl/flask-server-1tx0kkn/9796db1e2ac24761b456e686761a55ac [2023-05-31 21:28:30 +0000]  [INFO] Booting worker with pid: 16
You can get the exact service name to use by clicking on the "Runtime Logs" button in the Flightcontrol dashboard to go to the AWS CloudWatch console.
In the screenshot below, the group name is
Because Flightcontrol uses the same ECS Task Definition for each deployment, you can use the same group name for all deployments of the same service.
You can use any other tools that work with CloudWatch logs for monitoring your deployments - Flightcontrol does not limit your access to the logs in any way.
When you write your applications, if you would prefer to send your logs to another service (such as a Splunk server), that is also possible, and not limited by Flightcontrol.