These checks are run with pypi "body_scan"
"biotech" is a fork of "body_scan"
("body_scan" checks are written with "unittest")
[SH] biotech internal-statusChecks are started simultaneously, unless "--simultaneous no"
paths: [
{
"path": "../status_1.py",
"empty": false,
"parsed": true,
"stats": {
"passes": 2,
"alarms": 1
},
"checks": [
{
"check": "check 1",
"passed": true,
"elapsed": [
4.054199962411076e-05,
"seconds"
]
},
{
"check": "check 2",
"passed": true,
"elapsed": [
1.72930003827787e-05,
"seconds"
]
},
{
"check": "check 3",
"passed": false,
"exception": "Exception('not 110%')",
"exception trace": [
"Traceback (most recent call last):",
" File \"/home/veganecology/.local/lib/python3.11/site-packages/biotech/processes/scan/process/keg/check.py\", line 68, in start",
" checks [ check ] ()",
" File \"\", line 13, in check_3",
"Exception: not 110%"
]
}
]
}
]
alarms: [
{
"path": "../status_1.py",
"checks": [
{
"check": "check 3",
"passed": false,
"exception": "Exception('not 110%')",
"exception trace": [
"Traceback (most recent call last):",
" File \"/home/veganecology/.local/lib/python3.11/site-packages/biotech/processes/scan/process/keg/check.py\", line 68, in start",
" checks [ check ] ()",
" File \"\", line 13, in check_3",
"Exception: not 110%"
]
}
]
}
]
stats: {
"alarms": 0,
"empty": 0,
"checks": {
"passes": 2,
"alarms": 1
}
}
It's recommended to run biotech programmatilly. An example of this can be found in the "advanced configurations" section of the documentation.
Bryan@Status600.com