Skip to main content

Generated from aind-library-template

Project description

aind_watchdog_service

Usage

Watchdog runs in the background (see deployment), and watches a directory for newly-created yaml files containing instructions to transfer files.

On a computer where the watchdog service is running, manifests can be submitted by creating a file in the right folder. To do this in your software, pip install aind-watchdog-service and use the aind_watchdog_service.models.ManifestConfig object to write your manifest file in the proper format. See the examples/ folder in this repo for more details.

Configuration

Watchdog is configured using SIPE's configuration zookeeper server. The configuration options are listed in /src/aind_watchdog_service/models/watch_config.py.

Monitoring

Watchdog logs can be monitored from the main SIPE logserver (http://eng-logtools:8080/?channel_filter=watchdog&hide=location,count) or this grafana dashboard.

Deployment

Deployment in the institute is handled by SIPE systems engineers, submit a SIPE Request if you need watchdog installed somewhere.

Github actions are used to compile aind-watchdog-service into an executable using pyinstaller. This executable is attached to a Github Release and uploaded to SIPE's software /releases storage, where it can be deployed to rigs in the institute.

Watchdog should be deployed on a SIPE-accessible rig via the install-aind_watchdog_service.yml ansible script. This will download the app and set up a windows scheduled task to run the service. By default, the scheduled task includes a nightly restart at 11:30pm. If the task is running, the scheduler will kill the old instance and start the new one - due to how task scheduler force kills processes, the death of an old process will not generate a stop log.

Testing

Watchdog has a bundled test function that will create some dummy data on the rig and create a manifest file to transfer that data. Once Run it with the below commands:

cd "C://Program Files/AIBS_MPE/aind_watchdog_service"
aind_watchdog_service.exe --test

It will print something like the following:

Data created at C:\ProgramData\AIBS_MPE\aind_watchdog_service\logs\test_data
Manifest created at C:\Users\svc_mpe\Documents\aind_watchdog_service\manifest\test_manifest_2024-11-15_17-31-25.yml

Make sure that the running instance of watchdog picks up the manifest and completes the transfer.

Development

Clone the repo Install dependencies with uv sync --extra service --extra dev Run the service with uv run src/aind_watchdog_service/main.py

(If not using uv, use pip install .[service] and python src/aind_watchdog_service/main.py)

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

aind_watchdog_service-0.1.9.dev1.tar.gz (390.9 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

aind_watchdog_service-0.1.9.dev1-py3-none-any.whl (48.0 kB view details)

Uploaded Python 3

File details

Details for the file aind_watchdog_service-0.1.9.dev1.tar.gz.

File metadata

File hashes

Hashes for aind_watchdog_service-0.1.9.dev1.tar.gz
Algorithm Hash digest
SHA256 d56551513b990d7001c2c0b8dff4c2c50b8df38c6b9067db8d3dce4adf1d33f7
MD5 9745a0c0214ec4631c5f17ddff8d3393
BLAKE2b-256 2aa3fdd1ea7907ef56a40e2ffe31236ba01988702550c8e10c9744c91da828c2

See more details on using hashes here.

File details

Details for the file aind_watchdog_service-0.1.9.dev1-py3-none-any.whl.

File metadata

File hashes

Hashes for aind_watchdog_service-0.1.9.dev1-py3-none-any.whl
Algorithm Hash digest
SHA256 55bbd71802a715c8f48d028a9b0e708e506e22392e30975a0b9bf73ab537a4af
MD5 43b7711df6cda9c2d986cbb70cfb0881
BLAKE2b-256 64819583a1aa1be72dabeb6f8f65c112711a4ff1ff65182916fca4d1e542ed83

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page