Logprise
Logprise provides a one-stop logger for your Python application by integrating loguru and apprise. It intercepts all standard logging calls and routes them through a unified interface. Above a configurable threshold, errors are automatically sent as alerts via Slack, Discord, email, or 100+ other services - no code changes needed.
Why Logprise?
Your script crashes at 3 AM. You want to know about it immediately, not when you check logs tomorrow. Logprise automatically captures errors and sends them to your notification service of choice.
Works with your existing code: Logprise intercepts standard Python logging calls and redirects them through loguru. No need to refactor your codebase or update third-party libraries.
from logprise import logger
import logging
logger.error("Payment processing failed") # You get notified
logging.error("Database connection lost") # Also notified (auto-intercepted)
logger.warning("High memory usage") # Silent (unless configured)
Installation
pip install logprise
Quick Start
Step 1: Configure notification service (create ~/.apprise file):
mailto://user:pass@gmail.com
Step 2: Use it in your code:
from logprise import logger
logger.info("Script started")
logger.error("This triggers a notification") # Sent when program exits or after 1 hour
That's it. Errors automatically trigger notifications. No configuration needed beyond setting up your notification service.
Configuration
Notification Services
Apprise supports 100+ services. Configure them in ~/.apprise (or other standard locations):
# Email
mailto://user:pass@gmail.com
# Slack
slack://tokenA/tokenB/tokenC/#channel
# Discord
discord://webhook_id/webhook_token
# Telegram
tgram://bot_token/chat_id
See Apprise's service list for all options.
You can also add services programmatically:
from logprise import appriser
appriser.add("mailto://user:pass@gmail.com")
appriser.add(["slack://token/...", "discord://webhook/..."])
Notification Level
Control which log levels trigger notifications:
from logprise import appriser
appriser.notification_level = "WARNING" # Notify on WARNING and above
appriser.notification_level = "CRITICAL" # Only critical issues
appriser.notification_level = 30 # Numeric levels work too
Default is ERROR (30).
Timing Control
Notifications batch to prevent spam. Control when they're sent:
from logprise import appriser
# Change flush interval (default: 3600 seconds)
appriser.flush_interval = 1800 # Send every 30 minutes
# Send immediately
appriser.send_notification()
# Clear pending notifications without sending
appriser.clear()
Notifications automatically flush when your program exits.
Use Cases
Long-running scripts:
from logprise import logger
for item in large_dataset:
try:
process(item)
except Exception as e:
logger.error(f"Failed processing {item}: {e}")
# Notification sent, script continues
Scheduled jobs:
from logprise import logger, appriser
appriser.notification_level = "INFO" # Get notified of completion too
def daily_backup():
logger.info("Backup started")
# ... backup logic ...
logger.info("Backup completed")
Monitoring critical sections:
from logprise import logger
if disk_usage > 90:
logger.critical(f"Disk usage at {disk_usage}%")
# Immediate notification on program exit
Works with third-party libraries:
from logprise import logger
import requests
import logging
# Third-party libraries using standard logging are automatically captured
response = requests.get("https://api.example.com")
# If requests logs an error, you'll be notified
# Your existing logging code works too
logging.error("Custom error from standard logging")
logger.error("Error from loguru")
# Both trigger notifications
How It Works
- Automatic interception: Logprise intercepts both loguru and standard library
logging, redirecting all logs through a unified interface - Smart batching: Messages accumulate until flush interval or program exit
- Exception capture: Uncaught exceptions are logged and trigger immediate notification
- Multiple services: Send to multiple notification services simultaneously
This means third-party libraries using standard logging will also trigger notifications when they log errors.
Advanced Features
Prevent handler removal:
from logprise import logger
logger.remove() # Logprise handler persists automatically
Tagging for routing:
from logprise import appriser
appriser.add("discord://webhook/...", tag=["critical"])
appriser.add("mailto://...", tag=["all"])
Custom notification format:
from logprise import appriser
from apprise import NotifyType, NotifyFormat
appriser.send_notification(
title="Production Alert",
notify_type=NotifyType.FAILURE,
body_format=NotifyFormat.MARKDOWN
)
Testing with caplog
Loguru logs don't normally show up in pytest's built-in caplog fixture, because loguru bypasses the standard logging machinery that caplog hooks into. Logprise ships a pytest plugin that bridges this gap automatically - it's enabled the moment logprise is installed, with no configuration or conftest.py changes required.
Just use caplog as you always would:
import logging
from logprise import logger
def test_payment_failure_is_logged(caplog):
with caplog.at_level(logging.ERROR):
logger.error("Payment processing failed")
assert "Payment processing failed" in caplog.text
assert caplog.records[0].levelno == logging.ERROR
This works for logs from logprise.logger, from the standard logging module, and from third-party libraries - anything logprise intercepts. The caplog.at_level() context manager and level filtering behave exactly as they do with standard logging.
Contributing
git clone https://github.com/svaningelgem/logprise.git
cd logprise
poetry install
poetry run pytest
Contributions welcome via pull requests.
License
MIT License - see LICENSE file for details.
Metadata
Release files for logprise 1.4.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 |
|---|---|---|---|---|
| logprise-1.4.2.tar.gz | 14.9 kB | With provenance | Details for logprise-1.4.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| logprise-1.4.2-py3-none-any.whl | Python 3 | none | any | Details for logprise-1.4.2-py3-none-any.whl |
Total release size: 28.2 kB
Release files / logprise-1.4.2.tar.gz
| Download URL | logprise-1.4.2.tar.gz |
|---|---|
| Size | 14.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e4fa174752ab4334babbd40190ae2381f6c75bbe6a97ccf1e215704dcd33005
|
|
BLAKE2b-256 checksum How to use checksums |
ed234f8071a5bb0dcbf5d517e97788a181e4700e098425df86b95ebacdc87494
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 3, 2026.
Transparency logRelease files / logprise-1.4.2-py3-none-any.whl
| Download URL | logprise-1.4.2-py3-none-any.whl |
|---|---|
| Size | 13.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
18d2a4c3dfbef496ded73b340ba00e45e908bb50c2d0abac1b64bd11119d2dd6
|
|
BLAKE2b-256 checksum How to use checksums |
7a1e881b6a8df68ef0c797dbbeeec4a63f826c978ffccfd4ec6b4bc275b541c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 3, 2026.
Transparency logSecurity for logprise 1.4.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for logprise-1.4.2.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 Jun 3, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.