-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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/splunkhec] Support passing access token via context #37307
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@atoulme hello teacher antoine, could I help in resolving this issue? I can inject it into |
hi, when I started working on this issue, it seemed unassigned, and I wasn’t aware of others planning to address it. I’d love to hear any feedback or suggestions to improve the solution. |
You can take if you like, appreciated. This work is similar to what was done for SAPM receiver. I will review. |
hi @CodePrometheus , I will close this PR for now. Feel free to continue your work on this. |
Component(s)
receiver/splunkhec
Is your feature request related to a problem? Please describe.
The Splunk HEC receiver currently sets an access token passthrough value as a resource attribute on the payload.
Describe the solution you'd like
Instead, the receiver should set this value in the context of the request so it may be passed around to exporters without exposing a secret in the data.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: