You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The text was updated successfully, but these errors were encountered:
bpmct
changed the title
audit: how can I to programmatically consume the audit logs?
audit: how can I programmatically consume the audit logs?
Jan 2, 2023
@bpmct Is this ticket meant to track the work for the second checkbox you have listed: Server logs: coder server will export audited events to /dev/stderr by default or the documentation of that work, or both?
@Kira-Pilot - just the second part. As a docs reader, it's not particularly clear that the audit logs are also server logs and this is something we explain in v1. The MVP could be a couple of sentences in the audit docs.
Additionally, it would be nice for us to link to the API route docs from the overall audit docs.
It differs from #5356 because that issue is around the specific activities that are audited. This is info on how to consume them. If you still have questions about this, we can do a short huddle and write the docs live.
This issue is becoming stale. In order to keep the tracker readable and actionable, I'm going close to this issue in 7 days if there isn't more activity.
We need to document this :)
REST API: @mtojek is working on autogenerated docs for all the routes, including
/api/v2/audit
Tracked in Autogenerated docs for REST API #3522. For example:
Documented here: https://coder.com/docs/coder-oss/latest/api/audit#get-audit-logs
Server logs:
coder server
will export audited events to/dev/stderr
by defaultFor example:
In Coder v1, we have detailed documentation on exporting logs so we can use that as a reference.
The text was updated successfully, but these errors were encountered: