Heroku logs
Heroku logs are a stream of events which are collated and routed by Logplex. There are 3 types: API logs, system logs, and app logs.
Actions about the stack via the Heroku API are tracked by the API logs. Example:
| Code Block |
|---|
Sep 02 14:59:03 bridge-prod heroku/api: Deploy f158691 by xyz@abc.org |
System logs are events of the Heroku stack. Of particular interest is the router log:
| Code Block |
|---|
Sep 03 14:24:20 bridge-prod heroku/router: at=info method=GET path="/?study=api" host=webservices.sagebridge.org request_id=4f839190-0943-8a41-9081-5b9faa862f31 fwd="173.194.33.105" dyno=web.5 connect=4ms service=7ms status=200 bytes=509 |
...
TODO:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Logging and monitoring on AWS resources
We have CloudWatch alerts set up on DynamoDB metrics. For details, see the page Monitoring policies.
Access logging are enabled for the S3 buckets that store the upload data. Currently the logs are captured but not consumed.
TODO:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Another potentially useful service is CloudTrail which captures access to the AWS resources within the account.
TODO:
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|