Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Access logging #18

Closed
jamsajones opened this issue Nov 28, 2018 · 1 comment
Closed

Access logging #18

jamsajones opened this issue Nov 28, 2018 · 1 comment

Comments

@jamsajones
Copy link

Allow customers to enable HTTP/TCP access logging for a Virtual Node. Access logs will be written to a deterministic location in the Envoy container. This location can be shared with a log ingestion sidecar such as fluentd, or (for ECS and EKS) shared with the host and ingested by an agent running on the host (e.g. CloudWatch agent).
@coultn coultn changed the title Integration with CloudWatch Access logging Feb 12, 2019
@SleeperSmith
Copy link

Rather, can we have it streamed out via the gRPC ALS
https://www.envoyproxy.io/docs/envoy/latest/api-v2/config/accesslog/v2/als.proto#envoy-api-msg-config-accesslog-v2-httpgrpcaccesslogconfig

And have a service that sink it to CloudWatch Log directly? (Let us specify the log group please btw. We don't want auto generated log group littering our AWS account thanks)

@abby-fuller abby-fuller transferred this issue from aws/aws-app-mesh-examples Mar 27, 2019
@ewbankkit ewbankkit mentioned this issue Mar 28, 2019
Closed
@coultn coultn closed this as completed Mar 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kiranmeduri @jamsajones @SleeperSmith @coultn