Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "monitoring/alert system" #350

Open
yarikoptic opened this issue Apr 5, 2024 · 2 comments
Open

Add "monitoring/alert system" #350

yarikoptic opened this issue Apr 5, 2024 · 2 comments

Comments

@yarikoptic
Copy link
Member

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
Copy link
Collaborator

@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
Copy link
Collaborator

@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

- ${WORKER_PATH_AT_HOST}/data/cache:/data/cache
. You can add another line such as - <PATH__CONTAINING_DATASETS_IN_HOST>:<TARGETED_DIR_IN_THE_WORKER_CONTAINER>.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants