product-example 2 linked patterns checked

GitHub Docs: Using the audit log API for your enterprise

Documents API access, date-range querying, retention windows, UTC epoch timestamps, and activity records for enterprise audit logs.

Read with a purpose

What this source can teach

Use this source to inspect a concrete implementation and the decisions visible in its context.

  1. Start with the original. Open the source and find the guidance or example relevant to your task.
  2. Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
  3. Check the setting. Compare the source's platform, people, and constraints with your own decision.

Pattern Decisions This Source Supports

Pattern Supported decision Required contract Claim note
Activity log Choose activity log when the task is evidence review, investigation, compliance, security monitoring, or operational troubleshooting. Each log row identifies one recorded event and keeps actor, action, object, timestamp, and event ID stable across filtering, sorting, expansion, export, and refresh. GitHub supports date-range querying, retention windows, API record access, and UTC timestamp handling.
Audit log Choose audit log when the record must support governed security, compliance, forensic, or administrator-accountability review. Each audit row represents one governed audit record and keeps audit ID, actor, action, object, effective time, result, and retention metadata stable across filters, details, export, and API retrieval. Supports enterprise audit API access, retention windows, UTC timestamps, date/action/actor queries, pagination, and rate limits.

Comparisons supported by this source

Evidence Role

This source is treated as product-example evidence. Its value comes from the specific claims and setting described above.

Publisher: GitHub Docs. Last checked: .

Saved items