datalad / datalad-registry

MIT License
0 stars 2 forks source link

Add "monitoring/alert system" #350

Open yarikoptic opened 7 months ago

yarikoptic commented 7 months ago

Usecase from @jkosciessa if datalad-registry is used "locally" to register local repos, and the idea is to provide also some specification for monitoring various repos (e.g. in local directories as URL) and setting up alert system within datalad-registry to alert whenever that particular location storage demand exceeds some limit.

candleindark commented 7 months ago

@yarikoptic We can try this out in an ad-hoc manner for now, but for the long run, I think it would be a good idea to associate this kind of feature with an individual user after introducing a user system to Datalad-Registry.

candleindark commented 7 months ago

@jkosciessa I forgot to mention since all the services in Datalad-Registry run in isolated environment of containers. They don't have access to the filesystem or network of the host running Datalad-Registry by default.

If you have datasets residing in your system that you want to submit to a local Datalad-Registry, you can use bind mount to give the worker service access to the dataset. For example, after https://github.com/datalad/datalad-registry/blob/4da200b67004c034148944713ee445031f31989e/docker-compose.yml#L47. You can add another line such as - <PATH__CONTAINING_DATASETS_IN_HOST>:<TARGETED_DIR_IN_THE_WORKER_CONTAINER>.