Skip to content
New issue

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

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

Already on GitHub? # to your account

TrafficLog v2 #2007

Closed
bdecoste opened this issue May 19, 2021 · 5 comments
Closed

TrafficLog v2 #2007

bdecoste opened this issue May 19, 2021 · 5 comments
Labels
kind/design Design doc or related triage/duplicated already exists

Comments

@bdecoste
Copy link
Contributor

Summary

I'd like to use a TrafficLog policy (i.e. Envoy Access Logging) to enable access logs for destination services/DPPs. Currently only source DPPs are enabled for access logging via a TrafficLog policy.

Only outbound listeners are configured for access logging.

Steps To Reproduce

Note in the attached config_dump that inbound:echo-service_default_svc_8080 is not configured for access logging while all outbound listeners have access logging configured.

config_dump.txt

@jakubdyszkiewicz
Copy link
Contributor

xref #271

@github-actions
Copy link
Contributor

This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Nov 23, 2021
@lahabana lahabana removed the triage/stale Inactive for some time. It will be triaged again label May 30, 2022
@lahabana lahabana changed the title Support TrafficLog/Envoy Access Logs for destination DPPs TrafficLog v2 May 30, 2022
@lahabana lahabana added triage/accepted The issue was reviewed and is complete enough to start working on it kind/design Design doc or related labels May 30, 2022
@lahabana
Copy link
Contributor

lahabana commented May 30, 2022

The new version of traffic log should support both inbound and outbound accessLog.

@github-actions
Copy link
Contributor

github-actions bot commented Jul 1, 2022

This issue was inactive for 30 days it will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant please comment on it promptly or attend the next triage meeting.

@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jul 1, 2022
@lahabana lahabana removed the triage/stale Inactive for some time. It will be triaged again label Jul 4, 2022
@lahabana
Copy link
Contributor

lahabana commented Aug 2, 2022

Duplicate of #4733

@lahabana lahabana marked this as a duplicate of #4733 Aug 2, 2022
@lahabana lahabana closed this as not planned Won't fix, can't repro, duplicate, stale Aug 2, 2022
@lahabana lahabana added triage/duplicated already exists and removed triage/accepted The issue was reviewed and is complete enough to start working on it labels Aug 2, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
kind/design Design doc or related triage/duplicated already exists
Projects
None yet
Development

No branches or pull requests

3 participants