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

Jump to bottom

logging config uses defaultBackend in mesh config when we use enabledBackend in other policies #3242

Closed
lahabana opened this issue Nov 22, 2021 · 6 comments
Closed

logging config uses defaultBackend in mesh config when we use enabledBackend in other policies #3242

lahabana opened this issue Nov 22, 2021 · 6 comments
Labels
area/observability breaking-change kind/bug A bug triage/rotten closed due to lack of information for too long, rejected feature...

Comments

@lahabana
Copy link
Contributor

What happened?

For example:

type: Mesh
name: default
logging:
  defaultBackend: file
  backends:
    - name: logstash

We usually use enabledBackend
@lahabana lahabana added breaking-changes triage/pending This issue will be looked at on the next triage meeting kind/bug A bug kind/improvement Improvement on an existing feature area/observability and removed kind/improvement Improvement on an existing feature labels Nov 22, 2021
@lahabana
Copy link
Contributor Author

Another option: remove defaultBackend for Tracing and make the backend always required in TrafficTrace.

@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 Dec 30, 2021
@lahabana lahabana added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting triage/stale Inactive for some time. It will be triaged again labels Jan 17, 2022
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Feb 17, 2022
@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.

@lahabana lahabana removed the triage/stale Inactive for some time. It will be triaged again label Jul 5, 2022
@lahabana lahabana mentioned this issue Aug 2, 2022
Closed
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Oct 4, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Oct 4, 2022

This issue was inactive for 90 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 or attend the next triage meeting.

@lahabana lahabana added triage/rotten closed due to lack of information for too long, rejected feature... and removed triage/accepted The issue was reviewed and is complete enough to start working on it triage/stale Inactive for some time. It will be triaged again labels Oct 5, 2022
@lahabana
Copy link
Contributor Author

lahabana commented Oct 5, 2022

This is getting fixed with the new policies

@lahabana lahabana closed this as not planned Won't fix, can't repro, duplicate, stale Oct 5, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Oct 5, 2022

Automatically closing the issue due to having one of the "closed state label".

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
area/observability breaking-change kind/bug A bug triage/rotten closed due to lack of information for too long, rejected feature...
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lahabana