This release is a pre-release and may not be stable for production use.
opssignal
Turn application and workflow events into routed operational notifications: Slack, webhooks, PagerDuty, Microsoft Teams, Opsgenie, email and the console, from one event model. The routing, retry and delivery logic is a Rust core, so it behaves the same from Python, the CLI and the C library.
Status: beta. The Python bindings with the Airflow and dbt adapters are the tested path today.
Install
pip install --pre opssignal # local and https:// configs
pip install --pre 'opssignal[aws]' # + S3, AppConfig, DynamoDB, Secrets Manager, SES
pip install --pre 'opssignal[gcp]' # + Cloud Storage, Firestore, Secret Manager
pip install --pre 'opssignal[azure]' # + Blob Storage, App Configuration, Cosmos DB, Key Vault
pip install --pre 'opssignal[all]' # all three clouds
Wheels cover CPython 3.9 and later on Linux (x86_64, aarch64, glibc and musl), macOS on Apple Silicon and Windows x86_64. Other platforms, such as Intel Macs, build from the sdist, which needs a Rust toolchain.
Send a signal
import opssignal
opssignal.notify(
source="billing-api",
event_type="payment_failed",
title="Card declined for order 1042",
severity="error",
)
Airflow
from opssignal.integrations.airflow import failure_callback
default_args = {"on_failure_callback": failure_callback}
Route it
Point SIGNAL_CONFIG at a signal.yaml (a local path, https://, s3://,
gs://, az:// and more), or put one in the working directory:
providers:
slack:
webhook_url: "${SLACK_WEBHOOK_URL}"
routes:
- match:
severity: [error, critical]
environment: prod
providers: [slack]
No config, or no matching route? Signals go to the console, so nothing is silently dropped.
Links
- Documentation: https://adithyapathipaka.github.io/OpsSignal/1.0.0-beta.2/
- Source and issues: https://github.com/adithyapathipaka/OpsSignal
- License: Apache-2.0
Metadata
Release files for opssignal 1.0.0b2
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 | |
|---|---|---|---|---|
| opssignal-1.0.0b2.tar.gz | 122.2 kB | With provenance | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| opssignal-1.0.0b2-cp39-abi3-win_amd64.whl | CPython 3.9 | abi3 | Windows x86-64 | Details |
| opssignal-1.0.0b2-cp39-abi3-musllinux_1_2_x86_64.whl | CPython 3.9 | abi3 | Linux musl 1.2+ x86-64 | Details |
| opssignal-1.0.0b2-cp39-abi3-musllinux_1_2_aarch64.whl | CPython 3.9 | abi3 | Linux musl 1.2+ ARM64 | Details |
| opssignal-1.0.0b2-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ x86-64 | Details |
| opssignal-1.0.0b2-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | CPython 3.9 | abi3 | Linux glibc 2.17+ ARM64 | Details |
| opssignal-1.0.0b2-cp39-abi3-macosx_11_0_arm64.whl | CPython 3.9 | abi3 | macOS 11.0+ ARM64 | Details |
Total release size: 22.7 MB
Release files / opssignal-1.0.0b2.tar.gz
| Download URL | opssignal-1.0.0b2.tar.gz |
|---|---|
| Size | 122.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
25f234390e953694601ae473827cc8736bc6be3d0338afd33ff14a3111424537
|
|
BLAKE2b-256 checksum How to use checksums |
8a78d30e8678cff503ee58c8593efedf0566577a13d29df84f7249a1b33b6999
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / opssignal-1.0.0b2-cp39-abi3-win_amd64.whl
| Download URL | opssignal-1.0.0b2-cp39-abi3-win_amd64.whl |
|---|---|
| Size | 3.6 MB |
| Tags | CPython 3.9 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
de08c0475c75fb2de44fb5a3f0a7ea68edaf9ad049c7506e9e2f3f779d854967
|
|
BLAKE2b-256 checksum How to use checksums |
05fcc7f65fd7af0aa563f28bd303cc88a43d01439bd8639da1073211a786de9a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / opssignal-1.0.0b2-cp39-abi3-musllinux_1_2_x86_64.whl
| Download URL | opssignal-1.0.0b2-cp39-abi3-musllinux_1_2_x86_64.whl |
|---|---|
| Size | 4.1 MB |
| Tags | CPython 3.9 Linux musl 1.2+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
f80eee39987fa01579892b498d5a2e7d23b97e4df653d617311ba68efbce2cf2
|
|
BLAKE2b-256 checksum How to use checksums |
d2757f6978154734a614f488517e33d2a592eca70f72e532d37616cad1e490ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / opssignal-1.0.0b2-cp39-abi3-musllinux_1_2_aarch64.whl
| Download URL | opssignal-1.0.0b2-cp39-abi3-musllinux_1_2_aarch64.whl |
|---|---|
| Size | 3.9 MB |
| Tags | CPython 3.9 Linux musl 1.2+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
3201d0a3f5cd77cfd424a0a445a9b4b4a18374fa2b1bfcdf54507e6dd291a3aa
|
|
BLAKE2b-256 checksum How to use checksums |
70849b1fcad97231f5a046f709c7ec112e6819bbb6074cfe82fa372f15d51617
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / opssignal-1.0.0b2-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | opssignal-1.0.0b2-cp39-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 3.8 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
7e12d14c39aa24b5afea1144437cf3588fa0e3f1567d5670a8d0aa8ffe920eb0
|
|
BLAKE2b-256 checksum How to use checksums |
77164abe350990e137472a47dc66cbe2dc998008c9fc0333d6f493c337e2bb9b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / opssignal-1.0.0b2-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | opssignal-1.0.0b2-cp39-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 3.8 MB |
| Tags | CPython 3.9 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
87a61eec55407557e317eb9e2c3f31a6a48d1e88e181a23b932d1196e46821d1
|
|
BLAKE2b-256 checksum How to use checksums |
824018fdbda85038a4a9aa6af4d480d2b8adac69287db5b27be558826ac64fd0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / opssignal-1.0.0b2-cp39-abi3-macosx_11_0_arm64.whl
| Download URL | opssignal-1.0.0b2-cp39-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 3.5 MB |
| Tags | CPython 3.9 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
5f4cc9ea321b92afb2a28999643d301b4650644b7a36ce9926476718297555ac
|
|
BLAKE2b-256 checksum How to use checksums |
1b41e14db84e76f004b94596815b13c78211830e0c7ad277825de3ea5060081f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for opssignal 1.0.0b2
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.
Full provenance
All 7 files in this release have been uploaded with provenance metadata.
Attestation for opssignal-1.0.0b2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA 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.