The audit log allows organization admins to quickly review the actions performed by members of your organization. It includes details such as who performed the action, what the action was, and when it was performed.
Accessing the audit log
The audit log lists events triggered by activities that affect your organization within the current month and previous six months. Only owners can access an organization's audit log.
By default, only events from the past three months are displayed. To view older events, you must specify a date range with the created parameter. 詳しい情報については、「検索構文を理解する」を参照してください。
In the top right corner of GitHub Enterprise Server, click your profile photo, then click Your organizations.
Organizationの隣のSettings(設定)をクリックしてください。
設定のサイドバーで、Audit logをクリックしてください。
Searching the audit log
The name for each audit log entry is composed of the action object or category qualifier, followed by an operation type. For example, the repo.create entry refers to the create operation on the repo category.
各 Audit log エントリには、次のようなイベントに関する適切な情報が表示されます:
The enterprise or organization an action was performed in
Contains organization-level configuration activities for Dependabotセキュリティアップデート in existing repositories. For more information, see "Configuring Dependabotセキュリティアップデート."
Contains activities related to GitHub Actions workflows.
You can search for specific sets of actions using these terms. For example:
action:team finds all events grouped within the team category.
-action:hook excludes all events in the webhook category.
Each category has a set of associated actions that you can filter on. For example:
action:team.create finds all events where a team was created.
-action:hook.events_changed excludes all events where the events on a webhook have been altered.
Search based on time of action
Use the created qualifier to filter events in the audit log based on when they occurred. 日付の形式は ISO8601標準に従い、YYYY-MM-DD(年-月-日) とする必要があります。 オプションの時間情報のTHH:MM:SS+00:00を日付の後に付けて、時、分、秒で検索できるようにすることもできます。 これはTの後にHH:MM:SS(時-分-秒)、そしてUTCオフセット(+00:00)を続けたものです。
created:2014-07-08 finds all events that occurred on July 8th, 2014.
created:>=2014-07-08 finds all events that occurred on or after July 8th, 2014.
created:<=2014-07-08 finds all events that occurred on or before July 8th, 2014.
created:2014-07-01..2014-07-31 finds all events that occurred in the month of July 2014.
Note: The audit log contains data for the current month and every day of the previous six months.
Search based on location
Using the qualifier country, you can filter events in the audit log based on the originating country. You can use a country's two-letter short code or its full name. Keep in mind that countries with spaces in their name will need to be wrapped in quotation marks. For example:
country:de finds all events that occurred in Germany.
country:Mexico finds all events that occurred in Mexico.
country:"United States" all finds events that occurred in the United States.
Using the audit log API
You can interact with the audit log using the GraphQL API.
To ensure your intellectual property is secure, and you maintain compliance for your organization, you can use the audit log GraphQL API to keep copies of your audit log data and monitor:
Organizationもしくはリポジトリ設定へのアクセス
権限の変更
Organization、リポジトリ、Teamへのユーザの追加もしくは削除
管理者に昇格したユーザ
GitHub Appの権限の変更
The GraphQL response can include data for up to 90 to 120 days.
For example, you can make a GraphQL request to see all the new organization members added to your organization. For more information, see the "GraphQL API Audit Log."
Audit log actions
An overview of some of the most common actions that are recorded as events in the audit log.
Triggered when an existing hook has its configuration altered.
destroy
Triggered when an existing hook was removed from a repository.
events_changed
Triggered when the events on a hook have been altered.
integration_installation_request category actions
Action
Description
create
Triggered when an organization member requests that an organization owner install an integration for use in the organization.
close
Triggered when a request to install an integration for use in an organization is either approved or denied by an organization owner, or canceled by the organization member who opened the request.
issue category actions
Action
Description
destroy
Triggered when an organization owner or someone with admin permissions in a repository deletes an issue from an organization-owned repository.
Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "Checking the status of a self-hosted runner."
self_hosted_runner_offline
Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "Checking the status of a self-hosted runner."
self_hosted_runner_updated
Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "About self-hosted runners."
Triggered when GitHub Actions is enabled for a repository. Can be viewed using the UI. This event is not included when you access the audit log using the REST API. For more information, see "Using the REST API."
Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "Checking the status of a self-hosted runner."
self_hosted_runner_offline
Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "Checking the status of a self-hosted runner."
self_hosted_runner_updated
Triggered when the runner application is updated. Can be viewed using the REST API and the UI; not visible in the JSON/CSV export. For more information, see "About self-hosted runners."
Triggered when a repository transfer is about to occur.
unarchived
Triggered when a repository admin unarchives a repository.
update_actions_secret
Triggered when a GitHub Actions secret is updated.
repository_secret_scanning category actions
Action
Description
disable
Triggered when a repository owner or person with admin access to the repository disables secret scanning for a repository. For more information, see "About secret scanning."
enable
Triggered when a repository owner or person with admin access to the repository enables secret scanning for a repository.
repository_vulnerability_alert category actions
Action
Description
create
Triggered when GitHub Enterprise Server creates a Dependabot alert for a repository that uses a vulnerable dependency. For more information, see "About Dependabotアラート."
dismiss
Triggered when an organization owner or person with admin access to the repository dismisses a Dependabot alert about a vulnerable dependency.
resolve
Triggered when someone with write access to a repository pushes changes to update and resolve a vulnerability in a project dependency.
secret_scanning category actions
Action
Description
disable
Triggered when an organization owner disables secret scanning for all existing repositories. For more information, see "About secret scanning."
enable
Triggered when an organization owner enables secret scanning for all existing repositories.
secret_scanning_new_repos category actions
Action
Description
disable
Triggered when an organization owner disables secret scanning for all new repositories. For more information, see "About secret scanning."
enable
Triggered when an organization owner enables secret scanning for all new repositories.
team category actions
Action
Description
add_member
Triggered when a member of an organization is added to a team.
add_repository
Triggered when a team is given control of a repository.
Triggered when an organization owner enables team discussions for an organization.
workflows category actions
アクション
説明
cancel_workflow_run
ワークフローの実行がキャンセルされたときにトリガーされます。 For more information, see "Canceling a workflow."
completed_workflow_run
ワークフローのステータスがcompletedに変更されたときにトリガーされます。 REST APIを通じてのみ見ることができます。UIやJSON/CSVエクスポートでは見ることができません。 For more information, see "Viewing workflow run history."
created_workflow_run
ワークフローの実行が作成されたときにトリガーされます。 REST APIを通じてのみ見ることができます。UIやJSON/CSVエクスポートでは見ることができません。 For more information, see "Create an example workflow."
ワークフロージョブが開始されたときにトリガーされます。 ジョブに渡されたシークレットのリストを含みます。 Can only be viewed using the REST API. It is not visible in the the GitHub web interface or included in the JSON/CSV export. For more information, see "Events that trigger workflows."
approve_workflow_job
Triggered when a workflow job has been approved. For more information, see "Reviewing deployments."
reject_workflow_job
Triggered when a workflow job has been rejected. For more information, see "Reviewing deployments."