nextcloud / nextcloud/notify_push
Monitoring Capabilities inside NC
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 344
- Forks
- 64
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
After setting up notify_push, I miss the option of an easy way to figure out if everything works. I figured it out with the help of the Nextcloud Forum (https://help.nextcloud.com/t/how-to-verify-notify-push-works-correctly/116685/5) but still it would be great to see the 'metrics' information populated into the NC Admin Frontend.
Perhaps as part of the "server info" which is already existing on NC and shows system stats, connect users end software version information, or even as a separate entity with the connection status and metrics populated.
This would ease up knowing if the installation and the setup works. I would even go further and populate the "clients" using notify push in detail, so troubleshooting can be targeted.
This is another reference, where someone is requesting this integration / feature
https://github.com/nextcloud/notify_push/issues/59#issuecomment-796502759
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing notify_push's existing metrics and the Nextcloud Admin Frontend's server info area, then read the linked forum discussion and issue #59 comment. Done means administrators can inspect notify_push connection status and metrics in Nextcloud, with the desired client details defined and covered by the project's checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- frontend, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100