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

Receiver for Content-Security-Policy violation reports #18098

Closed
davispuh opened this issue Jan 30, 2023 · 4 comments
Closed

Receiver for Content-Security-Policy violation reports #18098

davispuh opened this issue Jan 30, 2023 · 4 comments
Labels

Comments

@davispuh
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Ability to collect Content-Security-Policy violation reports

Describe the solution you'd like
Point Content-Security-Policy: report-uri to OpenTelemetry Collector.
If this was supported then wouldn't need any additional code/service.

Describe alternatives you've considered
Write them to file and use filelogreceiver (maybe there's a better way?)

Additional context

For more info about CSP see:

@jpkrohling jpkrohling transferred this issue from open-telemetry/opentelemetry-collector Jan 30, 2023
@jpkrohling jpkrohling added the Sponsor Needed New component seeking sponsor label Jan 30, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Apr 3, 2023

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 Apr 3, 2023
@davispuh
Copy link
Contributor Author

davispuh commented Apr 3, 2023

I see that receiver/webhookevent have been merged (#19377). Any thoughts how this could be supported on top of it?

@github-actions github-actions bot removed the Stale label May 26, 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
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 Sep 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants