> For the complete documentation index, see [llms.txt](https://docs.cortex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.io/configure/gitops/gitops-logs.md).

# GitOps logs

GitOps logs serve as a valuable tool to understand and monitor changes made specifically through GitOps within your workspace. This feature provides a comprehensive record of changes made via GitOps. This record includes, but is not limited to, which repository a change was made in, the commit details, the number of commits made, the entities affected, and any validation errors that occurred during the change process.

GitOps logs are a great way for you to track changes, identify discrepancies, and gain a holistic view of changes that have been made in your workspace. You can access the GitOps log through the Cortex UI or the public API endpoint.

## Accessing GitOps logs through the Cortex UI

To view GitOps logs, navigate to [**Settings > GitOps** **logs**](https://app.getcortexapp.com/admin/settings/gitops-logs).

<figure><img src="/files/WIahrsh8uglipquunf0C" alt=""><figcaption></figcaption></figure>

The GitOps logs page lists events and associated details. Click into a log to view a side panel with more information:

* **Repo:** Name of the repository a change was made in.
* **Timestamp**: When the change was made.
* **Commit sha:** Record of the changes made in associated repository.
* **Branch**: Which branch the change was made in.
* **# of commits:** Total number of commits.
* Under the **Changes** tab, a list of the affected files.
  * You can toggle on **Show only with impacted entities** to view changes that impacted entities.
* Under the **Omitted files** tab, a list of files that were omitted during the commit.
* Under the **Event processing tab**, a list of related events.

![A GitOps log displays relevant information about the activity.](/files/18uyeHNAH33kmcya1Iu4)

### Accessing Audit logs through the public API endpoint

GitOps logs can also be accessed through the public API endpoint. Please refer to our [GitOps logs API documentation](/api/readme/gitops-logs.md) to learn how to retrieve GitOps logs.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cortex.io/configure/gitops/gitops-logs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
