Accessing the audit log
The audit log lists events triggered by activities that affect your organization within the last 90 days. Only owners can access an organization's audit log.
- In der oberen rechten Ecke von GitHub Enterprise Server klicke auf Dein Profilfoto und dann auf your profile (Dein Profil).
- Klicke auf der linken Seite Deiner Profilseite unter „Organizations" (Organisationen) auf das Symbol für Deine Organisation.
- Klicke unter Deinem Organisationsnamen auf Settings (Einstellungen).
- Klicke auf der Seitenleiste „Settings“ (Einstellungen) auf Audit log (Auditprotokoll).
Searching the audit log
Das Protokoll enthält die folgenden Informationen zu jeder Aktion:
- an welchem Repository eine Aktion durchgeführt wurde,
- der Benutzer, der die Aktion durchgeführt hat
- die Aktion, die durchgeführt wurde,
- in welchem Land die Aktion durchgeführt wurde,
- Datum und Uhrzeit der Aktion.
Beachte, dass Du nicht mit Text nach Einträgen suchen kannst. Du kannst jedoch Suchabfragen mit den verschiedensten Filtern erstellen. Viele Operatoren, die für die Abfrage des Log verwendet werden - wie z.B. -
, >
oder <
- haben das gleiche Format wie die Suche über GitHub Enterprise Server. Weitere Informationen findest Du unter „Suchen nach GitHub.“
Vorgangsbasierte Suche
Verwende den Qualifizierer operation
(Vorgang) um Aktionen für spezifische Typen von Vorgängen zu beschränken. Ein Beispiel:
operation:access
(Vorgangszugriffe) findet alle Ereignisse, bei denen auf eine Ressource zugegriffen wurde.operation:authentication
(Vorgangsauthentifizierung) findet alle Ereignisse, bei denen ein Authentifizierungsereignis durchgeführt wurde.operation:create
(Vorgangserstellung) findet alle Ereignisse, bei denen eine Ressource erstellt wurde.operation:modify
(Vorgangsveränderung) findet alle Ereignisse, bei denen eine vorhandene Ressource verändert wurde.operation:remove
(Vorgangsentfernung) findet alle Ereignisse, bei denen eine vorhandene Ressource entfernt wurde.operation:restore
(Vorgangswiederherstellung) findet alle Ereignisse, bei denen eine vorhandene Ressource wiederhergestellt wurde.operation:transfer
(Vorgangsübertragung) findet alle Ereignisse, bei denen eine vorhandene Ressource übertragen wurde.
Suche basierend auf Repository
Verwende den Qualifizierer repo
(Repository) um Aktionen auf ein spezifisches Repository einzuschränken. Ein Beispiel:
repo:my-org/our-repo
findet alle Ereignisse, die im Repositoryour-repo
der Organisationmy-org
aufgetreten sind.repo:my-org/our-repo repo:my-org/another-repo
findet alle Ereignisse, die in den Repositorysour-repo
undanother-repo
der Organisationmy-org
aufgetreten sind.-repo:my-org/not-this-repo
schließt alle Ereignisse aus, die im Repositorynot-this-repo
der Organisationmy-org
aufgetreten sind.
Beachte, dass Du den Kontonamen im Qualifizierer repo
einfügen musst; nur nach repo:our-repo
zu suchen, wird nicht funktionieren.
Suche nach Benutzer
Der Qualifizierer actor
(Akteur) kann Ereignisse einschränken basierend darauf, wer die Aktion durchgeführt hat. Ein Beispiel:
actor:octocat
findet alle Ereignisse in Verbindung mit Aktionen, die vonoctocat
ausgeführt wurden.actor:octocat actor:hubot
findet alle Ereignisse in Verbindung mit Aktionen, die vonoctocat
oderhubot
ausgeführt wurden.-actor:hubot
schließt alle Ereignisse in Verbindung mit Aktionen aus, die vonhubot
ausgeführt wurden.
Beachten Sie, dass Sie nur den in GitHub Enterprise Server verwendeten Benutzernamen, nicht den wirklichen Namen eines Benutzers, verwenden können.
Search based on the action performed
To search for specific events, use the action
qualifier in your query. Actions listed in the audit log are grouped within the following categories:
Category name | Description |
---|---|
discussion_post | Contains all activities related to discussions posted to a team page. |
discussion_post_reply | Contains all activities related to replies to discussions posted to a team page. |
hook | Contains all activities related to webhooks. |
integration_installation_request | Contains all activities related to organization member requests for owners to approve integrations for use in the organization. |
issue | Contains activities related to deleting an issue. |
org | Contains activities related to organization membership. |
organization_label | Contains all activities related to default labels for repositories in your organization. |
oauth_application | Contains all activities related to OAuth Apps. |
profile_picture | Contains all activities related to your organization's profile picture. |
project | Contains all activities related to project boards. |
protected_branch | Contains all activities related to protected branches. |
repo | Contains activities related to the repositories owned by your organization. |
repository_dependency_graph | Contains repository-level activities related to enabling or disabling the dependency graph for a repository. For more information, see "About the dependency graph." |
repository_vulnerability_alert | Contains all activities related to Dependabot alerts for vulnerable dependencies. |
team | Contains all activities related to teams in your organization. |
team_discussions | Contains activities related to managing team discussions for an organization. |
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. Die Datumsformatierung muss dem ISO8601-Standard entsprechen, der YYYY-MM-DD
(Jahr-Monat-Tag) ist. Du kannst nach dem Datum auch optionale Zeitinformationen THH:MM:SS+00:00
hinzufügen, um nach der Stunde, Minute und Sekunde zu suchen. Das ist T
, gefolgt von HH:MM:SS
(Stunden:Minuten:Sekunden) und einem UTC-Offset (+00:00
).
When you search for a date, you can use greater than, less than, and range qualifiers to further filter results. For more information, see "Understanding the search syntax."
For example:
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.
The audit log contains data for the past 90 days, but you can use the created
qualifier to search for events earlier than that.
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.
Note: The audit log GraphQL API is available for organizations using GitHub Enterprise.
To ensure a secure IP and maintain compliance for your organization, you can use the audit log GraphQL API to keep copies of your audit log data and monitor:
- Zugriff auf Deine Organisation oder Deine Repository-Einstellungen
- Changes in permissions
- Added or removed users in an organization, repository, or team
- Users being promoted to admin
- Changes to permissions of a 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.
discussion_post
category actions
Action | Description |
---|---|
update | Triggered when a team discussion post is edited. |
destroy | Triggered when a team discussion post is deleted. |
discussion_post_reply
category actions
Action | Description |
---|---|
update | Triggered when a reply to a team discussion post is edited. |
destroy | Triggered when a reply to a team discussion post is deleted. |
hook
category actions
Action | Description |
---|---|
create | Triggered when a new hook was added to a repository owned by your organization. |
config_changed | 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. |
org
category actions
Action | Description |
---|---|
disable_member_team_creation_permission | Triggered when an organization owner limits team creation to owners. For more information, see "Setting team creation permissions in your organization." |
disable_two_factor_requirement | Triggered when an owner disables a two-factor authentication requirement for all members and outside collaborators in an organization. |
enable_member_team_creation_permission | Triggered when an organization owner allows members to create teams. For more information, see "Setting team creation permissions in your organization." |
enable_two_factor_requirement | Triggered when an owner requires two-factor authentication for all members and outside collaborators in an organization. |
invite_member | Triggered when a new user was invited to join your organization. |
remove_member | Triggered when an owner removes a member from an organization or when two-factor authentication is required in an organization and an organization member doesn't use 2FA or disables 2FA. Also triggered when an organization member removes themselves from an organization. |
remove_outside_collaborator | Triggered when an owner removes an outside collaborator from an organization or when two-factor authentication is required in an organization and an outside collaborator does not use 2FA or disables 2FA. |
update_default_repository_permission | Triggered when an owner changes the default repository permission level for organization members. |
update_member | Triggered when an owner changes a person's role from owner to member or member to owner. |
update_member_repository_creation_permission | Triggered when an owner changes the create repository permission for organization members. |
organization_label
category actions
Action | Description |
---|---|
create | Triggered when a default label is created. |
update | Triggered when a default label is edited. |
destroy | Triggered when a default label is deleted. |
oauth_application
category actions
Action | Description |
---|---|
create | Triggered when a new OAuth App is created. |
destroy | Triggered when an existing OAuth App is deleted. |
reset_secret | Triggered when an OAuth App's client secret is reset. |
revoke_tokens | Triggered when an OAuth App's user tokens are revoked. |
transfer | Triggered when an existing OAuth App is transferred to a new organization. |
profile_picture
category actions
Action | Description |
---|---|
update | Triggered when you set or update your organization's profile picture. |
project
category actions
Action | Description |
---|---|
create | Triggered when a project board is created. |
link | Triggered when a repository is linked to a project board. |
rename | Triggered when a project board is renamed. |
update | Triggered when a project board is updated. |
delete | Triggered when a project board is deleted. |
unlink | Triggered when a repository is unlinked from a project board. |
update_org_permission | Triggered when the base-level permission for all organization members is changed or removed. |
update_team_permission | Triggered when a team's project board permission level is changed or when a team is added or removed from a project board. |
update_user_permission | Triggered when an organization member or outside collaborator is added to or removed from a project board or has their permission level changed. |
protected_branch
category actions
Action | Description |
---|---|
create | Triggered when branch protection is enabled on a branch. |
destroy | Triggered when branch protection is disabled on a branch. |
update_admin_enforced | Triggered when branch protection is enforced for repository administrators. |
update_require_code_owner_review | Triggered when enforcement of required Code Owner review is updated on a branch. |
dismiss_stale_reviews | Triggered when enforcement of dismissing stale pull requests is updated on a branch. |
update_signature_requirement_enforcement_level | Triggered when enforcement of required commit signing is updated on a branch. |
update_pull_request_reviews_enforcement_level | Triggered when enforcement of required pull request reviews is updated on a branch. |
update_required_status_checks_enforcement_level | Triggered when enforcement of required status checks is updated on a branch. |
update_strict_required_status_checks_policy | Triggered when the requirement for a branch to be up to date before merging is changed. |
rejected_ref_update | Triggered when a branch update attempt is rejected. |
policy_override | Triggered when a branch protection requirement is overridden by a repository administrator. |
update_allow_force_pushes_enforcement_level | Triggered when force pushes are enabled or disabled for a protected branch. |
update_allow_deletions_enforcement_level | Triggered when branch deletion is enabled or disabled for a protected branch. |
update_linear_history_requirement_enforcement_level | Triggered when required linear commit history is enabled or disabled for a protected branch. |
repo
category actions
Action | Description |
---|---|
access | Triggered when a user changes the visibility of a repository in the organization. |
add_member | Triggered when a user accepts an invitation to have collaboration access to a repository. |
add_topic | Triggered when a repository admin adds a topic to a repository. |
archived | Triggered when a repository admin archives a repository. |
config.disable_anonymous_git_access | Triggered when anonymous Git read access is disabled in a public repository. |
config.enable_anonymous_git_access | Triggered when anonymous Git read access is enabled in a public repository. |
config.lock_anonymous_git_access | Triggered when a repository's anonymous Git read access setting is locked. |
config.unlock_anonymous_git_access | Triggered when a repository's anonymous Git read access setting is unlocked. |
create | Triggered when a new repository is created. |
destroy | Triggered when a repository is deleted. |
enable | Triggered when a repository is reenabled. |
remove_member | Triggered when a user is removed from a repository as a collaborator. |
remove_topic | Triggered when a repository admin removes a topic from a repository. |
rename | Triggered when a repository is renamed. |
transfer | Triggered when a repository is transferred. |
transfer_start | Triggered when a repository transfer is about to occur. |
unarchived | Triggered when a repository admin unarchives a repository. |
repository_dependency_graph
category actions
Action | Description |
---|---|
disable | Triggered when a repository owner or person with admin access to the repository disables the dependency graph for a repository. For more information, see "About the dependency graph." |
enable | Triggered when a repository owner or person with admin access to the repository enables the dependency graph for a repository. |
repository_vulnerability_alert
category actions
Action | Description |
---|---|
create | Triggered when GitHub Enterprise Server creates a security alert for a repository that uses a vulnerable dependency. For more information, see "About alerts for vulnerable dependencies." |
dismiss | Triggered when an organization owner or person with admin access to the repository dismisses a security 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. |
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. |
change_parent_team | Triggered when a child team is created or a child team's parent is changed. |
change_privacy | Triggered when a team's privacy level is changed. |
create | Triggered when a new team is created. |
destroy | Triggered when a team is deleted from the organization. |
remove_member | Triggered when a member of an organization is removed from a team. |
remove_repository | Triggered when a repository is no longer under a team's control. |
team_discussions
category actions
Action | Description |
---|---|
disable | Triggered when an organization owner disables team discussions for an organization. For more information, see "Disabling team discussions for your organization." |
enable | Triggered when an organization owner enables team discussions for an organization. |