Monitoring in GitHub
Configure monitoring in GitHub
GitHub's Insights surface the health of the repository and the process around it, rather than the running application.
| Insight | Shows |
|---|---|
| Pulse | Recent activity summary |
| Contributors | Commit activity over time |
| Traffic | Clones and views |
| Dependency graph | What the project depends on, and what depends on it |
| Code scanning / secret scanning alerts | Security findings over time |
| Actions usage | Workflow runs, duration, failure rate |
What to watch
Actions usage is the operational one: run duration and failure rate over time are the pipeline-health metrics from Unit 3, seen through GitHub's lens.
The dependency graph underpins Dependabot — it is how GitHub knows which advisories apply to you. A project whose manifest is not parsed correctly gets no alerts, and the absence looks identical to having no vulnerabilities.
Charts
Organisation-level insights allow custom charts over activity data, so a platform team can track adoption of a practice — how many repositories have code scanning enabled, for instance — rather than inspecting repositories one at a time.
The gap to remember
None of this tells you whether the application is healthy in production. GitHub Insights covers the repository and the pipeline; Azure Monitor and Application Insights cover the running service. A complete instrumentation strategy needs both.
Primary sources