fastalert
Usage
Installation
Install latest from the GitHub repository:
$ pip install git+https://github.com/AnswerDotAI/fastalert.git
or from pypi
$ pip install fastalert
Documentation
Documentation can be found hosted on this GitHub repository’s pages. Additionally you can find package manager specific guidelines on pypi respectively.
How to use
To start your fastalert server, you can run the following in your terminal:
!fastalert --port 6001
Link: http://localhost:6001
INFO: Will watch for changes in these directories: ['/home/natedawg/aai-ws/fastalert/nbs']
INFO: Uvicorn running on http://0.0.0.0:6001 (Press CTRL+C to quit)
INFO: Started reloader process [64466] using WatchFiles
INFO: Started server process [64502]
INFO: Waiting for application startup.
INFO: Application startup complete.
^C
INFO: Shutting down
INFO: Waiting for application shutdown.
INFO: Application shutdown complete.
INFO: Finished server process [64502]
INFO: Stopping reloader process [64466]
fastalert supports token based authentication. To enable authentication, store your token in FASTALERT_API_KEY environment variable before starting your fastalert server.
fastalert supports two kinds of alerts. Immediate and heartbeat. Immediate alerts does not wait any set amount of time before sending the alert whereas heartbeat alerts wait a specific amount of time and can be canceled. To configure an immediate alert, you need to provide the name and the url you want to be alerted:
!curl -X POST http://localhost:6001/alert -H 'Content-Type: application/json' -d '{"name": "test", "url": "https://httpbingo.org/post"}'
The url will be send a post request with the following data: {"content": "An alert has been triggered for test.".
For heartbeats, you send to also specify the time to wait in seconds before triggering the alert:
!curl -X POST http://localhost:6001/heartbeat -H 'Content-Type: application/json' -d '{"name": "test", "url": "https://httpbingo.org/post", "ttl": 5}'
Resending a post request to the heartbeat route will cancel the previous alert timer for the alert with the same name and rearm the new one with the provided ttl.
Metadata
Release files for fastalert 0.0.2
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 |
|---|---|---|---|---|
| fastalert-0.0.2.tar.gz | 8.2 kB | Without provenance | Details for fastalert-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fastalert-0.0.2-py3-none-any.whl | Python 3 | none | any | Details for fastalert-0.0.2-py3-none-any.whl |
Total release size: 17.0 kB
Release files / fastalert-0.0.2.tar.gz
| Download URL | fastalert-0.0.2.tar.gz |
|---|---|
| Size | 8.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2c51816c172cc771e2046cc421bae19c6b705e2a4f18f0fc46e37b509698fe99
|
|
BLAKE2b-256 checksum How to use checksums |
7d4736bac77550f610828447793daf442103ec918e89b10dc26302e58af54f01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.5
|
Release files / fastalert-0.0.2-py3-none-any.whl
| Download URL | fastalert-0.0.2-py3-none-any.whl |
|---|---|
| Size | 8.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
56e24c20ddaa50a2918c6ee3ce708f00db41ebf64e1c7af28fc1321b19a8f14b
|
|
BLAKE2b-256 checksum How to use checksums |
5a745c4ea51acb98e16829ed4ab60a9c8acf8792bba639f0fddf889224d52816
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.5
|
Security for fastalert 0.0.2
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.