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.

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

[cmd/opampsupervisor] Properly handle Collector logs #21072

Open
evan-bradley opened this issue Apr 19, 2023 · 3 comments
Open

[cmd/opampsupervisor] Properly handle Collector logs #21072

evan-bradley opened this issue Apr 19, 2023 · 3 comments
Labels
enhancement New feature or request never stale Issues marked with this label will be never staled and automatically removed

Comments

@evan-bradley
Copy link
Contributor

Component(s)

No response

Is your feature request related to a problem? Please describe.

The Supervisor needs to receive the Collector's logs and allow forwarding them to an OTLP backend. The details for this are described in the Supervisor design document.

Describe the solution you'd like

Determine a viable approach for how to handle the Collector's logs and document this approach in the Collector design document. The work to implement this in the Supervisor can either be tracked through this issue or through one or more new issues after an approach has been agreed upon.

Describe alternatives you've considered

No response

Additional context

No response

@evan-bradley evan-bradley added the enhancement New feature or request label Apr 19, 2023
@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@github-actions github-actions bot added the Stale label Jun 19, 2023
@mwear mwear removed the Stale label Jun 21, 2023
@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@github-actions github-actions bot added the Stale label Aug 21, 2023
@github-actions
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 20, 2023
@evan-bradley evan-bradley reopened this Oct 24, 2023
@evan-bradley evan-bradley added never stale Issues marked with this label will be never staled and automatically removed and removed closed as inactive Stale labels Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request never stale Issues marked with this label will be never staled and automatically removed
Projects
None yet
Development

No branches or pull requests

2 participants