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.

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.

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 to learn how to retrieve GitOps logs.