openwisp/openwisp-monitoring
Network monitoring system written in Python and Django, designed to be extensible, programmable, scalable and easy to use by end users: once the system is configured, monitoring checks, alerts and metric collection happens automatically.
In plain words
Outside PRs: 8 in 10 merged. First reply usually within 37 h.
Outside PRs merged
80%
4 merged, 1 closed, 1 still open
Higher than 40% of 565 other measured repositories
Closed without merging (1)
First human reply
37 h
median of 6 outside PRs, 2 unanswered
Outside PRs opened 30 to 120 days ago, so each has had time to be answered. A figure needs at least 5 pull requests, otherwise it reads "Not enough data". How this is calculated · A number looks wrong?
Your first steps here
If you have never contributed to this project, do these in order.
- 1
Read the contributing guide
It says how to set the project up and what the maintainers expect in a pull request.
Open the guide - 2
Find something small
No first issue is free right now. Look for a typo, a missing test or an unclear error message, or ask where help is wanted.
Browse open issues - 3
Know where to ask
Questions go to the project's gitter, or on the issue itself. Not in private messages.
Open it - 4
Open a small pull request
Link the issue in it. A first reply here usually takes 37 h; until then, silence is normal.
What happens to an outside pull request
Every pull request opened by someone outside the core team, 30 to 120 days ago.
- Opened by outsiders6100%
- Got a human reply467%
- Merged467%
Time to first reply
After 2 days, 50% of outside PRs had a reply from a person. After a week, 50%. Bots do not count.
The last 52 weeks
Outside pull requests opened each week, and how many of them have been merged.
Starter issues
Issues labelled for beginners, with their real state. Available means open, unassigned, no linked pull request, nobody has claimed it in the last 14 days, and it was updated in the last 60 days.
- Available
- 0
- Claimed
- 0
- Has a pull request
- 5
- Stale
- 0
- Has a pull request[chores] Use theme colors from openwisp-utils variables#720
- Has a pull request[bug] REST API: device monitoring API mentions unused fields "example" and "Model"#716
- Has a pull request[bug] Dashboard API filters not shown in API docs/browsable API
When replies arrive
All maintainers counted together. Shown only when at least 3 people replied in the last 90 days, so it never describes one person.
Replies are most likely between 22:00 and 01:00 (India time).
Show as table
| Hour (India time) | Replies, all weekdays |
|---|---|
| 00:00 | 9 |
| 01:00 | 2 |
| 02:00 | 4 |
| 03:00 | 4 |
| 04:00 | 3 |
| 05:00 | 3 |
| 06:00 | 1 |
| 07:00 | 0 |
| 08:00 | 0 |
| 09:00 | 0 |
| 10:00 | 0 |
| 11:00 | 0 |
| 12:00 | 0 |
| 13:00 | 0 |
| 14:00 | 0 |
| 15:00 | 0 |
| 16:00 | 1 |
| 17:00 | 1 |
| 18:00 | 1 |
| 19:00 | 2 |
| 20:00 | 2 |
| 21:00 | 2 |
| 22:00 | 4 |
| 23:00 | 10 |
How to start
- Contributing guidefound
- Code of conductfound
- Issue templatesfound
- Dev container for one-step setupnot found
- No CLA or sign-off requirement was found.
Where the project talks
Activity
- Commits, 90 days
- 60
- Releases, 12 months
- 3
- Active maintainers
- 5
- Last push
- 3 Oct 2026
Stack
Similar repositories
Same main language (Python), most shared frameworks and topics first, then the faster reply.
Network and WiFi controller: provisioning, configuration management and updates, (pull via openwisp-config or push via SSH), x509 PKI manage
- First reply