This repository has been archived by the owner on Oct 24, 2020. It is now read-only.
Setup cloudwatch logging output for containers #27
Assignees
Labels
Comments
bbangert
added a commit
that referenced
this issue
Mar 17, 2017
Uses a CloudWatch LogGroup for ardere test plan runs. Also includes a refactor of the handler into a step_function file and a separate handler.py for Lambda as it requires some quirky path manipulation for AWS to see ardere as a top-level Python package. Closes #27
bbangert
added a commit
that referenced
this issue
Mar 17, 2017
Uses a CloudWatch LogGroup for ardere test plan runs. Also includes a refactor of the handler into a step_function file and a separate handler.py for Lambda as it requires some quirky path manipulation for AWS to see ardere as a top-level Python package. Closes #27
bbangert
added a commit
that referenced
this issue
Mar 17, 2017
Uses a CloudWatch LogGroup for ardere test plan runs. Also includes a refactor of the handler into a step_function file and a separate handler.py for Lambda as it requires some quirky path manipulation for AWS to see ardere as a top-level Python package. Closes #27
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We should log container stdout from the load-tests to Cloudwatch for review, likely using http://docs.aws.amazon.com/AmazonECS/latest/developerguide/using_awslogs.html
The text was updated successfully, but these errors were encountered: