Overview
After you connect your Harness entities to a Git repository, you can monitor Git synchronization and webhook activity from the Webhooks page.
The Webhooks page provides two tabs:
- Events: View the history of webhook events processed by Harness, inspect event details, and troubleshoot synchronization issues.
- Observability: Monitor repository synchronization health and Git provider API rate-limit consumption to identify configuration issues and maintain reliable synchronization. This tab is available at the account scope only.
What will you learn in this topic?
This section introduces the monitoring capabilities available on the Webhooks page. It covers:
- How to view webhook sync events.
- How to monitor repository synchronization health.
- How to monitor Git provider API rate-limit consumption.
Webhooks page
The Webhooks page provides two monitoring views.
Events
The Events tab displays the history of webhook events processed by Harness. You can monitor webhook activity, filter events, inspect payloads, and troubleshoot synchronization failures.
Go to Monitor webhook events to view and troubleshoot webhook events.
Observability
The Observability tab provides visibility into the health of Git synchronization and Git provider API usage across your repositories. It is available at the account scope only.
It includes:
- Repository sync health: View webhook coverage and synchronization status across Git-backed repositories.
- Rate limit consumption: Monitor Git provider API rate-limit usage for your Git connectors.
Go to Monitor repository sync health and Monitor Git provider rate limits to monitor synchronization and connector health.
Next steps
- Monitor webhook events: Monitor and troubleshoot webhook events.
- Monitor repository sync health: Monitor webhook coverage and synchronization status.
- Monitor Git provider rate limits: Monitor Git provider API rate-limit consumption.
- Set up bi-directional sync: Configure webhooks so Harness stays in sync with changes made directly in Git.