-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
feat: audit logging for Parseable #765
Labels
Comments
Is this issue still relevant @nitisht? If so, I wanted to take this up in my free time if that works. |
This has changed a little bit in scope @MihirLuthra . Let me update the description |
nitisht
changed the title
feat: create an internal log stream on parseable (s3 mode) only
feat: audit logging for Parseable
Sep 30, 2024
Thanks Nitish. I will pick this up. |
3 tasks
Exploring the possibility of implementing this through a tracing layer, I was able to implement this library: https://github.com/de-sh/audit-layer |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Audit logging is a core requirement for enterprise software. We need to add a feature to ensure a Parseable server (in any mode - local, s3, standalone, distributed) sends out audit logs to a target specified via env vars.
Env variables to add:
P_AUDIT_LOG_TARGET
-->String
, e.g.https://target.domain.name
P_AUDIT_LOG_TARGET_USERNAME
-->String
, e.g.user
P_AUDIT_LOG_TARGET_PASSWORD
-->String
, e.g.password
P_AUDIT_LOG_TARGET_TLS_VERIFY
-->Boolean
, e.g.false
P_AUDIT_LOG_TARGET_HEADERS
--> Command separated key value pair (String:String,String:String
), e.g.content-type:application/json, x-p-stream:audit
Also, we need to decide a schema of each audit log event. It should include
version
,eventType
and other relevant details.The text was updated successfully, but these errors were encountered: