Skip to main content

Generated from aind-library-template

Project description

aind_watchdog_service

Since the transfer of aind_watchdog_service into SIPE's control, it now lives and builds on SIPE's gitlab, with a mirror pushing updates to AllenNeuralDynamic's github repo.

It is published to pypi via a github action that runs when a Github Release is created.

Usage

Watchdog runs in the background, and watches a directory for newly-created yaml files containing instructions to transfer files. To use, 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

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.

When deploying on a new rig that had previously had the non-SIPE version of watchdog installed, extra care must be taken.

  • First, delete any scheduled tasks relating to watchdog. Some of these may be in a folder called "GUI Automation" or "AIND".
  • Next, run tasklist to check if there active watchdog processes, and kill them all with repeated use of taskkill /F /PID pid_of_the_process.
    • One running instance of watchdog will have two processes listed by tasklist
  • Install the new watchdog via ansible and check for a start log.
  • SSH in and run a self test with aind_watchdog_service.exe --test (see below) and make sure you see successful logs.

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

After cloning the repo, watchdog can be installed from source with pip install .[service], and run with 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.6.dev5.tar.gz (397.7 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.6.dev5-py3-none-any.whl (48.9 kB view details)

Uploaded Python 3

File details

Details for the file aind_watchdog_service-0.1.6.dev5.tar.gz.

File metadata

File hashes

Hashes for aind_watchdog_service-0.1.6.dev5.tar.gz
Algorithm Hash digest
SHA256 d878b560ee9462dcd444a3aca632bef24e2f4a5844cf8019a54a266941a1bb81
MD5 0f71bf8718c145793c5fb12140f3a18b
BLAKE2b-256 7535caec04ae95789b4ff3485ea87644109ba2c5cf15a3ebe35278835da93fd1

See more details on using hashes here.

File details

Details for the file aind_watchdog_service-0.1.6.dev5-py3-none-any.whl.

File metadata

File hashes

Hashes for aind_watchdog_service-0.1.6.dev5-py3-none-any.whl
Algorithm Hash digest
SHA256 883cbf93f98d277e46a0af6d7e4b713787d296a797d5b132fc2fef2880184489
MD5 495573e3ee72b4c97a439fa99c3752c1
BLAKE2b-256 38fac73b317bca080bf1c7556f9623b7f6a01096d08ec581b1e5595115a58cb2

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