Pioreactor Logs2Slack
This is a Pioreactor plugin to post a bioreactor's logs to a Slack channel.
Installation
This is a two part installation.
1. Setting up your Slack workspace
-
You probably want a dedicated channel for incoming logs, as it can get chatty. So go ahead and create a dedicated channel in your Slack workspace. I've called mine
experiment_logs. -
In Your Apps, click "Create New App" -> From "Scratch". Give it a name (something descriptive, like
Pioreactor Logs2Slack), and select the workspace. -
On the next page, select "Incoming Webhooks", and turn "Activate" to
On -
Click "Add new webhook to workspace"
-
In the next section, select the channel you made in step 1. Click "Allow".
-
On the next page, under "Webhook URL", is your new webhook URL, something like
https://hooks.slack.com/services/ABC.../124.... Important: this is private, don't share it with untrusted people, don't commit it into Github, etc.
2. Installing this plugin
-
In your Pioreactor interface, click on "Plugins". Find
pioreactor-logs2slack, and click "Install" beside it. Or you can runpio plugins install pioreactor-logs2slack. Either way, this plugin will be installed on your leader Pioreactor. -
After installing (should take less than a minute), click on "Configuration". At the bottom of the page will be a section called
[logs2slack].
[logs2slack]
slack_webhook_url=
log_level=INFO
Add your webhook URL from step 6. here. Click "Save". You can also change the level of logs to report, see Python logging levels.
-
Power-cycle (reboot) the Pioreactor leader, or ssh into the Pioreactor leader and run
sudo systemctl restart pioreactor_startup_run@logs2slack.service -
In your dedicated Slack channel, you should start to see logs arrive!
Metadata
Release files for pioreactor-logs2slack 0.5.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pioreactor_logs2slack-0.5.0.tar.gz | 4.1 kB | Without provenance | Details for pioreactor_logs2slack-0.5.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pioreactor_logs2slack-0.5.0-py3-none-any.whl | Python 3 | none | any | Details for pioreactor_logs2slack-0.5.0-py3-none-any.whl |
Total release size: 9.5 kB
Release files / pioreactor_logs2slack-0.5.0.tar.gz
| Download URL | pioreactor_logs2slack-0.5.0.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a05bb55033df000c53e7f7b3c8b993da60d1c04ffcf786e286752a91d12d8ba
|
|
BLAKE2b-256 checksum How to use checksums |
12ab2c9ff08dd23f6a226ac8a4cc7cb38223c042ab06ac6e75dac541c6a31559
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.0rc2
|
Release files / pioreactor_logs2slack-0.5.0-py3-none-any.whl
| Download URL | pioreactor_logs2slack-0.5.0-py3-none-any.whl |
|---|---|
| Size | 5.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
27e704b4a66990abd16407a9d307fcd115ac7a3b8c3eeea33aecba4f343a6d0f
|
|
BLAKE2b-256 checksum How to use checksums |
47181d6fa380bcab8162d4fd001a9ab147d2b51b705e141ee115a3bb9a3eb8d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.11.0rc2
|
Security for pioreactor-logs2slack 0.5.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.