MetaCell / MetaCell/cloud-harness
Monitor functionality on JupyterHub applications
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 5
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 3
Description
We have this internal tool and helm chart that we use on Netpyne to monitor the number of processes and the processes that are allowed to run in a specific pod and sends a message on a slack channel.
```
helm repo add psmonit https://prasus.github.io/helm-charts/
helm repo update
helm -n monitoring upgrade --install psmonit --set cluster=ecas2_cluster1 --set slackurl=https://hooks.slack.com/services/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 psmonit/psmonit
```
```
cluster: "ecas2_cluster1"
slackurl: "https://hooks.slack.com/services/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"
processlist: "tini|python|bash|netpyne"
processcount: "5"
ns: "netpyne"
```
It may be good to include this in order to control jupyter hub applications
Contributor guide
No contributing guide indexed for this repository
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
Review the referenced psmonit Helm chart, its cluster and process configuration, and how it sends Slack messages. Compare that functionality with the JupyterHub applications described in the issue and define which monitoring behavior should be included. Done means an agreed integration scope and a working way to monitor the targeted applications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, jupyter, kubernetes
- Domain
- infrastructure, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100